noah at coderanger
Sep 18, 2009, 1:55 AM
Post #2 of 3
(410 views)
Permalink
|
|
Re: Best website practice for multiple client and project Environments?
[In reply to]
|
|
Sounds fine to me. There are some scripts on trac-hacks already that
might help, but if your needs are simple making something yourself is
probably just as easy. I would be sure to read up on the [inherit]
config option and the corresponding --inherit argument to initenv
though.
--Noah
On Sep 17, 2009, at 11:52 AM, sem101 wrote:
>
> Hi Trac Users, I'm new. How's it going?
>
> I'm wondering the best way to setup multiple environments on a per
> client basis. How does this sound?
>
> /httpdocs
> -- trac (global trac env with svn to /var/svn/repos)
> ---- projects
> -------- client1 (trac env with svn to /var/svn/repos/client1)
> -------- client2 (trac env with svn to /var/svn/repos/client2)
> -------- client3 (trac env with svn to /var/svn/repos/client3)
>
> I've set it up like this and it seems to work fine. If this is not a
> bad way to perform this, I'm ready to automate the process with shell
> scripts and cron tasks. Each environment will have their own .egg-
> cache and the db directory will be owned by apache. I just don't wanna
> get started if I'm doing it wrong...
>
> Is this overkill? Is there a better/simpler way?
>
> Thanks in advance!
>
> Tai
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
|
