Mailing List Archive: Trac: Users

Multiple servers accessing single trac DB?

Index | Next | Previous | View Threaded

m.r.sanders at gmail

Nov 11, 2009, 8:01 AM

Post #1 of 2 (251 views)
Permalink

Multiple servers accessing single trac DB?

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?

Thanks,
Michael

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

doki_pen at doki-pen

Nov 14, 2009, 6:09 PM

Post #2 of 2 (220 views)
Permalink

Re: Multiple servers accessing single trac DB? [In reply to]

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 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
-~----------~----~----~----~------~----~------~--~---

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads