On Dec 7, 2007, at 16:25, Geoffrey Hoffman wrote:
> Here is my question. I have a Mac and my partner has a second Mac,
> and we're tag-teaming development on a WAMP (Windows Apache PHP
> MySQL) server on our LAN. That is, we both have the same network
> volume (WEBSERVER/www) mounted as a share on each of our Macs.
>
> Can we both work on one (shared network volume) working copy?
>
> It is working fine for me right now, and I just realized I wasn't
> sure how to add on another developer or if that was a bad idea
> altogether.
>
> I realize that it is _meant_ for two developers to each have their
> own working copy - but I'd rather not have two copies of this site
> on our WAMP. Does that make sense? In other words, on my box I've
> done:
>
> svn checkout [RepoURLOmitted] MyBox:/Volumes/WORKGROUP;WEBSERVER/
> www/site.com
>
> ... can my colleague do...
>
> svn checkout [RepoURLOmitted] HisBox:/Volumes/WORKGROUP;WEBSERVER/
> www/site.com
>
> ... checking out his working copy to the same exact place on the
> network, so we can both work on the exact same working copy?
>
> or is this a dumb idea.
Don't do this. Each developer should have at least one working copy
all to themselves (and possibly more than one, if you want to work on
multiple separate changes at the same time). Having multiple
developers work from a single working copy defeats most of the
benefits of using Subversion. No, you cannot check out one working
copy to the same place as another working copy. Engineer your site so
that it runs regardless of its URL. Then, you can put your working
copies under your public_html directory in your home directory, named
whatever you like. For example, consider this structure on your server:
/users/
you/
public_html/
main_wc/
new_feature_wc/
anotherdeveloper/
public_html/
main_wc/
some_bugfix_wc/
You can access these in the web browser this way:
http://server/~you/main_wc/
or
http://server/~anotherdevelopr/some_bugfix_wc/
Another option would be to keep the working copies locally on your
Macs, and set up Apache, PHP and MySQL on your local machines too.
This is the recommended way according to normal Subversion use, but
it can be inconvenient to have to maintain the configuration of that
software as well, not to mention that if you'd have to develop cross-
platform, making sure you write code that works on Windows PHP as
well as Mac/Unix PHP, which you may not have been planning to do
otherwise.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 7 23:41:50 2007