Set migration-dir or scope / internals.migrationMode from config with -e option?

[LiamKarlMitchell]

Hi just trying to figure out how to use db-migrate in a simple way.
I have a database.json in a config directory, postgresql so a connection string for a user that has ownership of a database schema I want to work with.

Is there a way to do something like this?

database.json

{
  "myConnection":
  {
    "connectionString": "etc...",
    "migrationMode": "myMode",
    "migrations-dir":  "./migrations/myConnection"
  }
}

So that when I do

db-migrate create something

It would create in

./migrations/myConnection/myMode/date-something.js

Or even just a migration directory setting per connection config would be nice.

./migrations/myConnection/date-something.js

I feel writing so much is not ideal would be nice to just write simple command to up or create new migration.

db-migrate create something --config=./config/database.json -v -e myConnection

Easier like this?

db-migrate create something -e myConnection
db-migrate up -e myConnection

Having it in database connection configs would allow to have multiple connections use the same migration scripts but have different databases/schemas.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[wzrdtales]

This is a good suggestion to be able to control this stuff per environment. However, the database.json is solely for the purpose of providing the database connection currently, so in that case we might need to rethink how this stuff actually works.

[wzrdtales]

We could consider also versioning the database.json and let a new schema take over. However, this would be semantically wrong, so probably nothing I would allow to do though. Maybe reworking configs in its entirety is not that wrong at all.

[LiamKarlMitchell]

Ended up plonking it in my projects package json.

Then we can use npm run tasks like this

npm run authdb-update
npm run authdb-create somechange

{
  "scripts": {
    "authdb-update": "db-migrate up --config=./config/database.json -e auth_owner --migrations-dir=./migrations/auth",
    "gamedb-update": "db-migrate up --config=./config/database.json -e game_owner --migrations-dir=./migrations/game",
    "authdb-add": "db-migrate --config=./config/database.json -e auth_owner --migrations-dir=./migrations/auth create ",
    "gamedb-add": "db-migrate --config=./config/database.json -e auth_owner --migrations-dir=./migrations/game create "
  }
}

[wzrdtales]

that is a way too, or MAKESCRIPTS, but still a good suggestion worth having a thought for.

[wzrdtales]

It is by the way planned that scopes can directly manage multiple dbs, but that is some future task. Currently you can only switch to a db on the same server via scope configs.

[LiamKarlMitchell]

Good to know thanks.