I fully agree with these beginning features: * database migrations * deployment on multiple servers * code synchronisation protocol abstraction * deployment through gateway servers * run system commands on remote servers * deploy only parts of the projects on servers (n frontend servers, n backend servers, etc) * rollbacks
On Wed, Jul 2, 2008 at 10:56 PM, Tristan Rivoallan <[EMAIL PROTECTED]> wrote: > > hey, > > On Wed, Jul 2, 2008 at 5:13 PM, Jonathan Wage <[EMAIL PROTECTED]> wrote: >> I have a few questions about the deploy task for 1.2 from you all. I would >> like to hear everyones opinion. >> >> - How far are we trying to take the deploy task this round? I read >> somewhere the goal is to have something on the level of capistrano. > > or a set of capistrano rules specialised in symfony deployment ? > >> - Do we want to integrate database migrations in to the programmable >> deploying interface? > >> - Will it have the ability to integrate with source control for >> tagging, branching, etc. and generate patches to deploy code changes? > > i think we should start with a very small code base that's capable of : > * obtain data (code) from a location > * synchronise data on some remote locations > * rollback > * exposes hooks for doing things prior / after data synchronisation > >> This one really interests me because in the past I have used >> capistrano for managing svn tags, branches and deploying upgrades/ >> downgrades to code with svn diff and patch. I have always wanted to >> take it one step further and tie in database migrations to the process >> because currently I still run the processes a part from each other. > > very interesting subject. i've been experimenting quite a lot too, and > (atm) the best system i've found is generating native package for the > operating system (rpm, deb, msi, ...). Do you think we should code a > deployment task that generate native packages (as python setuptools > does more or less) ? > > anyway, we need to gather all requirements. i'll set up a wiki page > from what we will get from this thread. > > here we go : > > * database migrations > * deployment on multiple servers > * code synchronisation protocol abstraction > * deployment through gateway servers > * run system commands on remote servers > * deploy only parts of the projects on servers (n frontend servers, n > backend servers, etc) > * rollbacks > * ... > > ++ > tristan > > -- > Tristan Rivoallan > http://www.clever-age.com > Clever Age - conseil en architecture technique > GSM: +33 6 219 219 33 Tél: +33 1 53 34 66 10 > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
