Roderick A. Anderson wrote:
I am installing RT (3.8.8) where PostgreSQL is running on another system
-- not a problem -- and the database (one of many company databases)
already exists with a schema to hold the RT tables. The roles (d...@acme
, rt_u...@acme) and their permissions are already set up as part of the
database provisioning.
OK a little more reading and I see this is already doable with arguments
to rt-setup-database script.
Sorry for the wasted bits, bytes and bandwidth.
Rod
--
I don't see anyway other than change the code in rt-setup-database to
connect to the 'company' database instead of template1 and just create
the tables, views, etc. in the schema.
I'm wondering if anyone else is interested in using RT in a multi-tenant
PostgreSQL database setup? If there is I'll look at coding to make the
database a 'configure' variable and the DSN method use it.
There are lots of other possibilities including:
* have the Pg superuser (postgres) check if the specified database
exists and error out if not,
* Create the rt3 schema if necessary,
* create the rt_user role etc.
Thoughts, ideas?
\\||/
Rod
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
