Best practices

[wayne marsh]

Hello everyone,

I've installed Trac on a NetBSD system and I'm trying to find information regarding where to put the trac folder for the projects we control via SVN.  My first thought is to put it in the root fo the working directory.

IE:
svn path = /svn
working directories path are:
/work/project1
/work/project2

With this setup
I was thinking of using trac-admin to set up Trac files for both projects in each of their directories.  So the commands I would use are something like:
mkdir /work/project1/Trac; \
mkdir /work/project2/Trac; \
sudo trac-admin /work/project1/Trac initenv; \
sudo trac-admin /work/project2/Trac initenv

Is this something like what is normally done?  Where do most people put their Trac environement folder?  Everywhere I looked it was some arbitrary path like the TracGuide /path/to/project.  I'm just using for best/most common practices, nothing fancy.

[RjOllos]

On Tuesday, June 19, 2012 10:35:33 AM UTC-7, wayne marsh wrote:

Is this something like what is normally done?  Where do most people put their Trac environement folder?  Everywhere I looked it was some arbitrary path like the TracGuide /path/to/project.  I'm just using for best/most common practices, nothing fancy.

/var/trac/$TRAC_ENV and /var/svn/$PROJ are what I've used, and I think it's fairly common.

[Olaf Meeuwissen]

RjOllos <ry...@physiosonics.com> writes:

> On Tuesday, June 19, 2012 10:35:33 AM UTC-7, wayne marsh wrote:
>
> Is this something like what is normally done? Where do most people put their Trac
> environement folder? Everywhere I looked it was some arbitrary path like the TracGuide /path

> /to/project. I'm just using for best/most common practices, nothing fancy.

>
> /var/trac/$TRAC_ENV and /var/svn/$PROJ are what I've used, and I think it's fairly common.

I've been using

/srv/projects/$PROJECT/
/srv/projects/$PROJECT/apache.conf # web server configuration snippet
/srv/projects/$PROJECT/trac/ # trac environment
/srv/projects/$PROJECT/svn/

for a site that serves multiple projects in a multi-env setup. Each
project has *all* of its data in that directory. The svn repositories
are made available via symlinks, like so:

/srv/repositories/svn/$PROJECT -> /srv/projects/$PROJECT/svn

and the apache.conf snippets for active projects are all included in the
web server's config. Project admins can *not* modify these, BTW.

BTW, the /srv/ directory is documented in the File Hierarchy Standard
(FHS)[1], but I don't know whether the BSDs pay any attention to that.

[1] http://www.pathname.com/fhs/pub/fhs-2.3.html#SRVDATAFORSERVICESPROVIDEDBYSYSTEM

Hope this helps,
--
Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962 Help support software freedom
http://www.fsf.org/jf?referrer=1962

[wayne marsh]

Thank you very much.

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.

To post to this group, send email to trac-...@googlegroups.com.
To unsubscribe from this group, send email to trac-users+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.