Sean Moss-Pultz wrote:
> On 2005/11/16, at 下午 3:31, Mike Dewhirst wrote:
>
>> Sean Moss-Pultz wrote:
>>
>>> My team is planning about a 2 to 3 week field test during which we
>>> will need to maintain a synced code base. Currently we are using
>>> subversion but we will not have access to this server on the road.
>>>
>>
>> Presumably, other teams will be working and making changes while you
>> are away.
>>
>>
>> IMHO the easiest solution would be to set up a new cheap subversion
>> server on a retired PC reformatted to run Linux off a magazine cover.
>> If you serve via apache you can set it up so everyone has
>> authenticated access from anywhere. The people left behind can cache
>> their logins for convenience.
Sorry Sean - I wasn't clear enough.
I think the new subversion server should be set up at home base in such
a way that it is externally accessible to you while away. At the same
time it would accessible to those who stay behind.
I skipped the (necessary) step of moving the repository to the new
'external' machine. I also skipped mentioning my assumption that the
current subversion server is on a protected network which cannot be made
accessible from outside.
On that note, it doesn't even have to be at home base. You could set it
up anywhere with a static IP address and decent DSL connection. If you
are only versioning text files it can be an indecent DSL :)
Mike
>>
>
> We are all going to be using notebooks. my is a powerbook so i could
> easily install a subversion server but then I'm not sure if it's
> possible to merge this new repository back into our existing one at
> work. It would be very important for us as work would be done on both
> repositories. Do you know if this would be possible?
>
> This is why I was thinking SVK could be a good solution.
>
> -Sean
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 16 09:03:50 2005