On Nov 9, 2011, at 8:53 AM, Lee Hambley wrote: > Then you have two independent projects, not two stages. > > I recommend using git submodules, still - and tracking your i18n separately, > and when you need to "deploy" your translations, make a one-liner task go to > the app, and do a `git submodule update`. Then Git (a content tracker) will > track when your translations were last deployed (or rather, what version was > last deployed, which I'd wager is just as important.) > > And your developers won't have to care about checking out and symlinking, and > keeping up to date two trees, and your deployments will always be a one-shot, > with an option to deploy translations when they become available without > requiring an extensive re-deploy of the whole I18n tree, and re-symlinking > into the project root. > > I guess my point is "use your tools" - symlinking/etc on the filesystem and > deploying two separate stacks, and symlinking codebases with > interdependencies is going to be horribly unreliable, and violates the > principle of least surprise (submodules were designed to solve this problem > (dependent projects with alternate release cycles)) so why not leverage them > to your advantage? > > Sounds like you're resisting a bit, because you are already invested in this > route, which I fear may be a mistake for you. ---- It's not my project - I'm just the plumber trying to fix the leaks. My boss likes to do things the way he likes to do things and I am trying to accommodate rather than to keep trying to finesse vlad
First off, git is a non-starter. The investment in subversion is rather extensive here, it works and the boss isn't really interested in getting everyone to learn a new system (let alone the disruption of migration). Secondly, we have a variety of 'staging/testing' type servers with which various tags are tested so we want to be able to choose which tags are deployed both for the main application and for the translations. Obviously the production servers are almost always using the main trunk for both code bases but all other servers - all bets are off. I am uncertain of the exact terminology of stages/projects etc. In essence, it is a single deployed application but with 2 different subversion code bases... 1 for the web application and 1 for the language translations and ultimately they are tied together with the deployment. Craig -- * You received this message because you are subscribed to the Google Groups "Capistrano" 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/capistrano?hl=en
