make sense, i just thought to be designer friendly :)
On Oct 15, 11:37 am, Andrew Scott <[EMAIL PROTECTED]> wrote: > I'll agree with Toby, for the same reasons. > > The problem is a good one, and it boils down to discipline on the designers. > You can have a share on a server for them to work with if you want daily > backups, but I would use it as a normal mapping for them to work with their > own work and use tortoise on their machines for revision controlling their > work. > > As for integration into the website, then you really need to put procedures > that best suits your needs and minimises the impact of other developers. > > Andrew Scott > Senior Coldfusion Developer > Aegeon Pty. Ltd.www.aegeon.com.au > Phone: +613 8676 4223 > Mobile: 0404 998 273 > > From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf > Of Toby Tremayne > Sent: Monday, 15 October 2007 11:16 AM > To: cfaussie@googlegroups.com > Subject: [cfaussie] Re: CF + Subversion best practices ? > > Andrea, > > I'd recommend against the shared repository - I went that way with a team a > few years ago and it was very painful. You have the difficulties of user > tracking etc, and when you start using tags and branches properly everything > goes to hell, but primarily we found using the dev server location for > actually committing was a real pain, as designers would regularly drop in > folders, overwrite things or move things about and totally stuff up the .svn > folders etc :) > > Let them have just a copy of the codebase on their machines so they can > update and commit their work, make sure your repository is automatically > publishing to the design server, and let the designers cut n paste their > files and folders across to test them, safest all round. > > Toby > > On 10/15/07, Andrea <[EMAIL PROTECTED]> wrote: > > Andrew... > That's exactly what I'm actually trying to achieve with solution > 3... :) > > I just do not want designers to have the need to install CF and apache > on their machines... designers will over-kill me ! .. that's why in > solution 3 they will work directly on the server (on a shared folder) > (committing their changes, but without having to install anything > except maybe tortoise) > > on the other way I was actually thinking to have tortoise installed on > the dev server (the xxx.dev site) so that they will not need to > create their repo/checkout ... but using a shared user that commit/ > update from the server itself (via remote connection, only when they > need to)... > > but this will also mean that to update the xxx.dev with a new > revision .... the only way would be to remote connect to the server > and do a checkout/update... > > <br --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
