Re: Howto handle remote repository creation in a Multi-Repository scenario

Ryan Schmidt wrote:
> I was also going to suggest that you should reconsider using a single
> repository for everything. Not only would i solve the problem of remote
> repository creation, but it would enable you to share code between
> projects, should that need ever arise. If you have every project in its
> own repository, you won't be sharing code between them -- at least, not
> preserving history.

Well, we do need to share code sometimes, but it is not important to
preserve history in those cases (cause the history of some code is not
relevant to another project).

> But since others have already made that suggestion and you've rejected
> it, I'll move on to answering your question:

Thanks.

> You mention you want to run mod_dav_svn on the NAS. This sounds like a
> rather sophisticated NAS box, then, if it can run custom Apache modules.

Well, i call it NAS for comfortability, but for real it is a "Network
Server".

> Hopefully that means you can also run other web software on the NAS box.

Yes, i could. I also considered using a webinterface.

> There is a web-based repository administration tool called SVNManager
> which may just do the trick for you. I haven't used it, but it says it
> can create and delete repositories, and more, so you should look into it:
>
> http://svnmanager.sourceforge.net/

Thanks for the tipp. I will have a look at this.

Patrick

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 15 09:28:09 2007