Well maybe I wasn't very clear. What I was thinking is having the automatic commit via webdav on a different repository (dev):
Basically this: User edits file through webdav. File gets saved to the dev repository (so every save, and every change is in this repository), and also saved to the disk. File gets tested through the browser in the regular way, and then committed through from the pc to the production repository. I'm not very sure how webdav is set up, so I'm assuming that the settings for that lie in apache instead of on the disk. This way I can have the same file in the dev repository and production repository at the same time. Is this possible? -----Original Message----- From: Barney Boisvert [mailto:[EMAIL PROTECTED] Sent: Monday, September 26, 2005 4:26 PM To: CF-Talk Subject: Re: source control setup I'd really, really, really recommend you don't do what you propose. By doing automatic commits (via webdav), you're going to be updating your repository on every save, which means that every time you save a file it's available to be synced to your production server. You explicitly say you DON'T want that behaviour, so stay away from that arrangement. If you don't want to use working directories per-developer that's fine (though foolhardy, if you ask me). However, you NEED to take a look at branches, as they're the only way you're going to get the security you want, because it will allow you to commit to the repository (to avoid losing work), without the code accidentally being sent into production until you're ready. cheers, barneyb On 9/26/05, Russ <[EMAIL PROTECTED]> wrote: > No, the copy of the code is on the dev server, and each developer edits the > code directly using ftp. As we are a small shop, we have not had a lot of > issues with people messing up each other's code. I am fine with all the > code being on the same server. > > We have some people working remotely, and having the code on each developers > laptop would be fairly hard to set up (we need to install iis, coldfusion, > and then the database would probably be an issue, as we'd have to access it > over the internet.) Although this would be possible in theory, it is > probably out of our reach for the time being. I am more worried about not > having a copy of the development branch in a repository until someone is > ready to deploy the code. We've had issues where the file was saved as a 0 > byte file and work had to start from the beginning or at least from an older > backup. > > Is anyone using the setup I'm talking about? I.e. Everything you save the > file through webdav, it goes into the repository and gets put into the file > system at the same time. Once we're ready to deploy stuff, it goes into a > different repository (production). Is this setup even possible? What I've > read so far leads me to believe that it is, but I wanted to see if anyone is > using it this way and if there are any gotchas, etc.. > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 100 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:219295 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
