Hi all Thanks for the input, I'll review the suggestions and get back..
Cheers Matt ---------------------------------------------- http://cenatus.org/ http://radialsolutions.co.uk/ ---------------------------------------------- On Wed, Jun 23, 2010 at 12:32 AM, Rem <[email protected]> wrote: > Hi Matt, > we use a similar process to Josh. Typically we might have content > going in, markup being worked on, and development occurring at the > same time. It might seem a bit of a hassle to have each person having > their own local dev at first, but it does seem to resolve a lot of > issues. Even if you don't have lots of different people working on > stuff, it might be a good practice to set up a process that allows for > this- so if it does occur then you won't descend into version hell :) > > We use Capistrano to grab a fresh version of the database, and then > rake tasks run as part of a deploy to update layouts from SVN. I'd > suggest having a look at Capistrano first before trying a GUI tool - > but of course it depends what you feel comfortable with. > > The only bit I'd add is to watch out for assets - these have caused us > grief in the past. Someone adds an asset to staging, and then layouts > break on Dev because this is missing and/or the IDs get messed up. So > we've added something in to allow a developer to grab a version of > assets. > > Here are parts of our deploy script - hope these are helpful for you: > asset synch > http://pastie.org/1015179 > grab db: > http://pastie.org/1015165 > > regards > > Ben > > http://redant.com.au > > On Jun 22, 11:36 pm, Josh French <[email protected]> wrote: >> I suspect the full answer involves getting your colleague to work with >> actual source control, but here's our general setup: >> >> * Multiple local development environments >> * A local staging server >> * Maybe a second staging server on the client's end >> * The final production server >> >
