-
Notifications
You must be signed in to change notification settings - Fork 31
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
git deploy to staging #116
Comments
Depends what. I made the blog and docs in a way that they refresh automatically (fs.watch) without restarting the server... |
True, just that in this case that I merged the disable of guides needed to On Sat, Oct 25, 2014 at 12:31 PM, Arian Stolwijk [email protected]
|
Yeah, iirc there was something when running in production that it doesn't recompile jade files or something.. |
I don't work with git, but I use auto update from svn. Website is a work copy from repository. Every hour run script on cron. Script run command "svn up". If you need, script may call some need action, for example build some file like css. |
Thanks but this would be under git, and yes a cron job would work but there It's a matter of getting it done, though. On Mon, Dec 1, 2014 at 9:20 AM, Enyby [email protected] wrote:
|
It's not the lack of examples. It's the requirement of a devops to prepare On Mon, Dec 1, 2014 at 5:29 PM, Enyby [email protected] wrote:
|
on post-receive (or appropriate) pull to staging, node build/all and restart
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: