In gmane.comp.version-control.subversion.trac.general, you wrote:
>
> I am looking in to ways of making the ticketing aspects of our Trac
> installation available to outside users without also having to host
> our SVN repository on an externally facing machine (as this is not an
> OSS project, and so would be a security risk).
>
> I am thinking in terms of the following architecture:
>
> Server 1 (inside firewall)
> - apache
> - trac, using DB hosted on server 2
> - svn
>
> Server 2 (in DMZ)
> - apache
> - trac, accessible to external users
> - trac DB (MySQL or PostgreSQL)
>
> Both instances of trac (on server 1 and server 2) would be pointed at
> the same DB running on server 2. Users accessing trac on Server 2
> would be limited to the ticketing system. Users accessing trac via
> server 1 would get the full works (ticketing, wiki, svn integration
> etc.)
>
> Could this work? Or would there be issues having two tracs use the
> same DB?
It works fine but you must you postgres
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
