Thanks for the info. I guess more to the point of what I was hoping for would be to share the same users and permissions across multiple different project environments, which would be great for right now but as I thought about it I realized that's really not at all what we want to do as we move forward and grow. It really seems like multiple databases would be more maintainable, as well as make it easier to recover from a backup if one project environment borks and corrupts the database.
Again, thanks for the response! -Travis On Wed, Nov 12, 2008 at 11:46 PM, Noah Kantrowitz <[EMAIL PROTECTED]>wrote: > > You can use a single database with a different schema for each > instance. Add ?schema=blah to the DB string I think (I'm sure someone > will correct me if I am wrong). > > --Noah > > On Nov 12, 2008, at 10:36 PM, Travis Veazey wrote: > > > I'm currently battling with getting Trac talking to my PostgreSQL > > server. I think I'm close to getting that figured out - it seems to > > be a matter of permissions within PostgreSQL now - but that's not > > the point of this e-mail. > > > > I will be having multiple Trac project environments. Will I need to > > create a separate PostgreSQL database for each, or can the project > > environments share one? > > > > That is, do I need to have databases like > > trac_project1 > > trac_project2 > > trac_project3 > > etc. > > > > Or can all the project environments simply point to one database like > > trac > > > > Thanks in advance for any insight! > > > > -Travis > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
