Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

set up dev-ops / server config #29

Open
oakmac opened this issue Nov 30, 2014 · 4 comments
Open

set up dev-ops / server config #29

oakmac opened this issue Nov 30, 2014 · 4 comments
Assignees

Comments

@oakmac
Copy link
Member

oakmac commented Nov 30, 2014

I need to set up some scripts and config with my web host in order to push updates to the site automatically with the running node server.

I have this already working for the cheatsheet, but the doc pages will need something more involved, which should be able to work with the entire site.

@oakmac oakmac self-assigned this Nov 30, 2014
@comamitc
Copy link

I have built something for my projects that might work... we could adapt it:

https://github.com/comamitc/build-server/blob/master/build.js

@comamitc
Copy link

comamitc commented Aug 4, 2015

@oakmac can you open source what you already have (or private bitbucket repo) so that I can dig into this one a bit more?

@oakmac
Copy link
Member Author

oakmac commented Aug 4, 2015

It's a very simple shell script similar to the one found here:
https://github.com/cljsinfo/cljs.info/blob/master/00-scrap/publish-cheatsheet.example.sh

In general, I want to keep this devops / server logic as simple as possible. Keep as much complexity in the CLJS code as possible.

@comamitc
Copy link

comamitc commented Aug 4, 2015

Nice - that's along the same lines of what I was thinking as well.

My previous build server would simply be listening with a github hook and when pushing to master it would git clone (which you are able to do to any public repo) and execute some kind of generic build script (let's call it ./build.sh). This would accomplish continuous deployment on the master branch.

The build script would probably only consist of one time grunt and lein tasks. In fact, we could embed grunt tasks in the project.clj so it only has to call one command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants