Re: Default folder names compulsory?
Date: Sun, 13 Jan 2008 16:12:17 +1100
At 08:22 AM 12/01/2008, Ryan Schmidt wrote:
>On Jan 11, 2008, at 05:57, an0n1m0us_at_gmail.com wrote:
Ok, that sounds like what I want but I don't think I've explained the context to you properly.
>Working copies are meant to be disposable. They can get wedged or
Hmmm, sometimes svn "wedges [the code] ... into weird states" ?
However I think there's a miscommunication re context here. /home/username/ is on the server, it's the project space, the project's VWS username. It's not the local machine's of developers.
>>If this is the case, my scenario would need a situation where any
As above, this isn't what I was intending. I was hoping to update a project's output space on the development server.
>Users should be in control of when and if to update their
Yeah I understand working copies on developers machines are best controlled by developers.
>It sounds like you're maybe not versioning regular source code
Website code. Our current workflow is:
Setup a Virtual Web Server (VWS) account for a customer (aka user, aka project) in the development server's home directory. Something like this:
would point to
on the development server.
Developers simply log in from their workstations via FTP and work carte blanche (in reality the only two developers currently sit next to each other and communicate re which files we touch) on any file by downloading it to our workstation, modifying, saving the changes (uploading) and previewing immediately via the above URL.
When a site is ready to go live, it is manually moved via FTP from the development server to a production server which is usually mapped to a corresponding VWS with a URL like:
What is lacking here is backup (aka versioning), collaborative development without relying purely on developer communication and a simplified way to move or merge development code from the development server to the production server. Eventually there might be a staging server in between as well. However that's not something I'm prepared to worry about just yet.
Hope this clears up the context/model of what I'm hoping we can set up.
Thanks for your continued help.
This is an archived mail posted to the Subversion Users mailing list.