Re:Dead Simple Rails Deployment
by tom on Monday June 01, 2009 @11:10AM
(#636187)
Why not just rsync -auvz?
Avoiding a small bit of initial frustration in setting up Capistrano, SSH keys etc, in order to have what feels like an easier deploy is a wonderful case of penny wise and pound foolish.
Take the time, do it right, get the benefits of a real deployment. It's worth it.
Re:Dead Simple Rails Deployment
by sant0sk1 on Monday June 01, 2009 @10:40AM
(#636140)
No worries, your joke gave me a chuckle too.
Looks like my wp-super-cache plugin is not working properly so every time the page is requested it regenerates the cache. No idea why but its pretty much killing the server.
Re:Dead Simple Rails Deployment
by bdotdub on Monday June 01, 2009 @11:21AM
(#636204)
Not sure about abyssknight, but they block random random things here at work (corporate america!). They've got weird rules and/or regexes for this stuff. Some of it makes no sense whatsoever
Avoiding a small bit of initial frustration in setting up Capistrano, SSH keys etc, in order to have what feels like an easier deploy is a wonderful case of penny wise and pound foolish.
Take the time, do it right, get the benefits of a real deployment. It's worth it.
Locally I do this 'git push repo master' then on the remote machine I run 'update.sh' which is here: http://pastie.org/496681
I tend to think that if you are going to bother with Capistrano you should go all the way..
I thought I had wp-super-cache enabled but maybe not. I'm giving it a reboot now so we'll see if that fixes things.
Looks like my wp-super-cache plugin is not working properly so every time the page is requested it regenerates the cache. No idea why but its pretty much killing the server.
svn commit -m "Added stuff."
cap:deploy