Multiple portals on one DB

[markrey]

To make it more manageable for multiple portals, we need to create db based on some UUID / random formats rather than static

Database name / schema can be dynamic and attached with the UI server.

production:
  adapter: postgresql
  encoding: unicode
  database: db/doc_prod
  pool: 5
  timeout: 5000

[Dee Koder]

Ah @markrey for this, I suggest deploying multiple instances of doctor. This would be more manageable than baking the instance details into the db.

[markrey]

For backup and management reasons, I do have only one DB. Which is very high performance one.

While deploying we can pass "db name, user , pass" as variables or in Heroku deployment, we can create it based on the script.

If this is just my scenario, i will create separate fork rather than main code change.

[Dee Koder]

ok sure thing.

[markrey]

Something like this can be an option as well.
https://github.com/influitive/apartment