search

foodcoop-adam / foodsoft

DEPRECATED, being merged in upstream. Web-based software for foodcoops - as used in NL.
http://foodcoop-adam.github.io/
Other
10 stars 3 forks source link

Documented deployment strategy / Auto deploy setup #38

Closed dokterbob closed 3 years ago

dokterbob commented 11 years ago

As we'll be working with multiple devs on a single project in our spare time, it is important that there is some deployment automation so all the devs can update and rollback deploys on demand, with a few simple commands so there is little risk of human error.

fsmanuel commented 11 years ago

what do u mean? something like capistrano?

dokterbob commented 11 years ago

Yep. Something like that would be ideal - but it's not just technology I am talking about. There should be a well-documented workflow on how and where updates are made (GIT branches etc) and preferably some kind of CI (see my ticket about Travis) as well.

fsmanuel commented 11 years ago

+1 sounds great!

wvengen commented 11 years ago

Yes!! An option would be to make the servers run git, and add post commit hooks to deploy pushes.

dokterbob commented 11 years ago

No, it is better to have the servers run a production-ready CI like Jenkins which is made for these kind of tasks. Travis is not stable enough and in any case we don't want untested code to go in production.

My personal preferance though would be to have a few simple shell commands to explitly tag production releases and perform deploys or rollbacks. I have implemented similar things in a Django/Python environment but do not know what the best tools of trade are for RoR.