One SVN, Multiple TRAC instances

[Jan Kraus]

Dear list,


I would like to ask whether it is possible to have multiple trac
instances bound to one svn repository.

Does it have some limitations or is it save. What is your opinion, or
could you please direct me to the right docs? I have searched all I
know, but only found topics of the opposite scenario.

With regards
Jan

[Peter O'Connell]

I may be ignoring the obvious, but why do you wish to have multiple trac
instances for 1 SVN? I assume it should be straight forward by simply
creating the trac instances and pointing each to the same SVN repos.

SolutionsPT is a trading name of SolutionsPT Limited, Registered office: Unit 1, Oakfield Road, Cheadle Royal Business Park, Cheadle, SK8 3GX
Registered in England & Wales Registration Number: 1937672

******************************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
******************************************************************************

[RJOllos]

On Sep 1, 8:12 am, "Peter O'Connell" <Peter.OConn...@solutionspt.com>
wrote:

> I may be ignoring the obvious, but why do you wish to have multiple trac
> instances for 1 SVN? I assume it should be straight forward by simply
> creating the trac instances and pointing each to the same SVN repos.

I'm also fairly sure there is no issue with this. You just configure
the second Trac instance the same you would the first. Multiple SVN,
single Trac is the much more difficult scenario (support for which I
believe is coming in 0.12 "multi-repos").

[stanleyxu2005]

Of course there is no problem at all.

One svn repos of mine looks as follows:
svn_repos
|-- lib1
|-- lib2
|-- proj1

I assume that you want to create different tracs for subdirs in a svn
repository
You can do that by running
trac-admin svn_repos/lib1 initenv
trac-admin svn_repos/lib2 initenv
trac-admin svn_repos/proj1 initenv

cheers

[Jan Kraus]

Hello,

I need to have different layers of information accfessible by different users - namely employees of a company versus stuidents working on various projects.
But I would like to keep just one source code tree.

PS: thanks for suggestions - al I needed to know is that there is no problem to operate multiple tracs over one svn repository.
JK

[jevans]

On Sep 7, 5:12 am, Jan Kraus <kra...@gmail.com> wrote:
> Hello,
>
> I need to have different layers of information accfessible by different
> users - namely employees of a company versus stuidents working on
> various projects.
> But I would like to keep just one source code tree.
>
> PS: thanks for suggestions - al I needed to know is that there is no
> problem to operate multiple tracs over one svn repository.
> JK

Not sure if you still have a question. If so, you may need to be more
specific about what you're trying to do.
- jevans

[RJOllos]

On Sep 7, 3:12 am, Jan Kraus <kra...@gmail.com> wrote:
> I need to have different layers of information accfessible by different
> users - namely employees of a company versus stuidents working on
> various projects.
> But I would like to keep just one source code tree.

Sounds like you may want to have a single repository and configure
access with path-based authorization [1]. It depends on your specific
circumstances, but I found that having a single repository and
configuring per-directory access permissions in the authz file was
much easier than having multiple repositories.

[1] http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html

[RJOllos]

> [1]http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauth...

Sorry, I confused myself with a different thread I was following
recently. I see this is not relevant to your setup.