Not a direct answer, but having implemented source control here recently and considered all these matters, I would say your setup is not ideal.
A better structure is to have developers working on their own workstations. Each PC/MAC is setup with its own web server and cf server running plus access to any dev databases. Each developer checksout a copy of the system they are working on and works on their assignment testing locally. They can do updates to see thier colleagues committed changes. Once they commit you can now checkout this code to a shared server for testing - I would rather call this the staging or test server. From here once tested you can deploy to live. This way you remove the ftp issue and take advantage of the SVN repository being the central copy of the code. Any code not checked in remains on the developers machine. You may want to consider using branches to cater for more major/longterm developments but that is a whole separate topic..... We use CVS rather than SVN but the principles are the same i believe. MikeT On 9/26/05, Russ <[EMAIL PROTECTED]> wrote: > > Tried posting this on Friday, but it never seemed to have made it through: > > > > We're already using subversion pretty successfully on our servers, but the > way we're using it, we're running into a few problems. > > > > We have a dev server, which has the production tree checked out, with > development changes made straight on the server through ftp. Once the code > is ready to be deployed, it gets committed to the repository, and then the > svn update is run on the production server (which also has the production > tree checked out). > > > > Now, if there is some code that is worked on for a long time, or never > gets > approved to be deployed, then we have code sitting on development for a > long > time and never being in source control. Sometimes ftp will screw up and > overwrite the file, and all the changes get lost. > > > > I heard that it's possible to set up svn with webdav through apache. Is it > possible to have a set up where we are editing files through webdav or > something, and every time we save it gets saved to the development branch > or > repository and also gets updated in the file system? Then once we're ready > to deploy, we would commit it to the production repository as usual. > > > > Also what editors support webdav? Homesite doesn't seem to support it, and > I've been using CFEclipse lately, which is a little buggy with the ftp > support, but I'm assuming there is a webdav plugin for it somewhere. Is it > possible to set it up through windows somehow? I read something about web > folders, but have not been able to figure out how to set it up in XP Pro. > > > > Russ > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:219263 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
