Hi Kevin and Jeremy. It sounds that it should be relatively painless.
Many thanks for your advice.
Regards,
David
Kevin Grover wrote:
> You can just start an svnserve or Apache (with mod_svn) process and
> others can access the repository (if they have permissions) via svn://
> or http://
>
> You can continue to use the file:// or switch to the other (your
> preference).
>
> It would make sense to switch if you have users/passwords set up through
> svnserve or apache (to prevent accidental mods via the file:// checked
> out code
>
> For Apache you have the passwd list and/or the svn authz file. I've
> used passwd but never authz. I'd guess the manual would be good at
> explaining that...
>
> - kevin
>
> On 12/22/06, *David Pratt* <fairwinds@eastlink.ca
> <mailto:fairwinds@eastlink.ca>> wrote:
>
> I have a repository I am using on a Mac using file:///path/to/my/repos.
> I am looking to have other developers access this remotely so will be
> transferring it to a server. Will anything need to be modified in
> existing repository for this work? I have not yet determined the best
> means of securing the code (to make it accessible to only the folks I
> want) at the moment. Advice on transferring and securing the repository
> would be appreciated.
>
> Regards,
> David
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> <mailto:users-unsubscribe@subversion.tigris.org>
> For additional commands, e-mail: users-help@subversion.tigris.org
> <mailto:users-help@subversion.tigris.org>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 22 23:41:42 2006