On 4/17/07, Justin Cook <justin@skull.co.nz> wrote:
> Hiya!
>
> I have a question regarding repository structure. I'm working on several
> projects and I was wondering what the best way to manage it is.
>
> Is it better to use one repository, or set up multiple ones? I was
> thinking of dividing my repos into coding, web and audio rather than
> making a repo for each job. Is this safe?
If it were me, I'd have different repositories. But it's personal
preference thing, not that one's any better than the other. If
they're really separate, then use separate repositories. If they're
related (one uses the other), then it may be easier to use a single
repository. There's no "right" answer.
Second: I'm using Collabnet's svn server, and it only seems to support
> one repo. Is there a way to get it to run more than one at once? Can I
> get it to run as a service rather than leaving a black command prompt up
> all the time on my fileserver? Would I be better off running it as an
> apache service?
I have our svnserve daemon servicing multiple repositories, and it's a
snap. Start the svnserve process using the -r command line parameter,
which tells it which directory to use when hosting repositories.
So, my I store my repositories in /ct/ctsvn/repositories (so,
/ct/ctsvb/repositories/repos1, /ct/ctsvn/repositories/repos2, etc).
Then, when I start svnserve, I pass it -r /ct/ctsvn/repositories. It
will serve all the repositories it finds within that directory. Works
like a treat.
Hope this helps,
Ed
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Apr 17 00:09:23 2007