News for hackers. Stuff that matters.
Re:Ask YC: Good resources for dev/staging/production config by wastedbrains on Thursday March 13, 2008 @11:56AM (#136023)
We use SVN, Rails, and Capistrano.

If you are using rails I highly recommend capistrano.

We each have our dev environment on our local machines including the DB.

We have a staging server which is at our place the staging server is the same OS (Debian), apache, ruby, rails, and updates as our production server. (We always perform system updates to this box and do test deployments before going to production).

We have our production servers off site.

deploying to either environment is fully automated with capistrano.

cap staging deploy cap production deploy

We mostly develop on the trunk, but when working on really large features that might take a few days or break significant amounts of the code / test, we then work in a branch. We often want the trunk in good shape in case any large bugs show on production and we need to start to work on fixes right away.

This works well for us, I am sure there is similar tools for Python and I do think keeping a separate staging server around your place is worth the trouble.

Re:Ask YC: Good resources for dev/staging/production config by iamelgringo on Thursday March 13, 2008 @12:33PM (#136056)
From what I've read. Capistrano is not Rails exclusive. You can use it to deploy other frameworks as well.
Re:Ask YC: Good resources for dev/staging/production config by whalesalad on Thursday March 13, 2008 @08:15PM (#136411)
Yeah, Capistrano is language exclusive, you can use it for anything. I have looked into it but never found it that exciting. I guess I need to revisit Capistrano :)
Re:Ask YC: Good resources for dev/staging/production config by tlrobinson on Friday March 14, 2008 @12:49AM (#136572)
Language agnostic?
Re:Ask YC: Good resources for dev/staging/production config by whalesalad on Friday March 14, 2008 @03:25AM (#136644)
Garrr. Yes, that's the word I was looking for. Thanks :)