If I understand you correctly, you've got each developer with a copy
of the source on their workstation, and then they FTP it to the dev
server?  That's a bad way to do it; you should have a working copy
per-developer, and keep them synchronized with svn, rather than using
FTP (since as you say, you can easily overwrite stuff).  If you
overwrite something with svn, which is very difficult to do
accidentally, you can always get it back, because everything is
versioned.  This will also alleviate the need to use webdav directly.

Second, you need to check out branches.  Branches let you do parallel
development, so if someone needs to go off in some new direction, they
can create a branch that doesn't interfere with anyone else (or the
production code), and then when they're all done, the branch's changes
can be merged back into the main line of development.  The benefit is
that while workin gon the branch, you can commit to the repository, so
you won't ever lose anything.

cheers,
barneyb

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
>
>

--
Barney Boisvert
[EMAIL PROTECTED]
360.319.6145
http://www.barneyb.com/

Got Gmail? I have 100 invites.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Discover CFTicket - The leading ColdFusion Help Desk and Trouble 
Ticket application

http://www.houseoffusion.com/banners/view.cfm?bannerid=48

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:219260
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

Reply via email to