Environment variables in config file

I have separate config json files for dev and prod, using the format

{
    "user": USER,
    "password": PASSWORD,
    "database": DATABASE_NAME
}

Using the command db-migrate up --config config/production.json -e prod how would I reference USER and PASSWORD from production.json in my database.json config file?

<bountysource-plugin>

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>

[wzrdtales]

@TGOlson Great to see, you have found a way that works for you and your team.

From what you’ve done I think, it would help to add a method to the programable API (there is no such API yet, but v0.10.x introduce one) that specifies a config object directly instead of parsing a file? In v0.10.x things like you have done now, are much easier, as there finally an API gets introduced that is made for the purpose of using db-migrate within another node.js module or in some automation.

Details about this are about to be documented soon, since yet there is only the instruction about the call convention over a singleton. http://db-migrate.readthedocs.org/en/latest/API/programable/

[TGOlson]

Hey fellas,

Just swinging by to say we solved our problem by wrapping calls to db-migrate in our build tool, Gulp. We basically load our own internal config, and then provide the environment specific db url to db-migrate. Something like this:

var config = require('../server/config');

var DB_MIGRATE_COMMAND = 'DATABASE_URL=' + config.db + ' ./node_modules/.bin/db-migrate';

gulp.task('migrate', shell.task(DB_MIGRATE_COMMAND));

I omitted some setup code for brevity (if anyone wants the full solution I’d be happy to provide it). We do a little more work to wrap the tasks so you can provide options, like up --count 2, etc., but in general this has worked very well, without having to do much code/data duplication.

Edit: in case it’s not clear, the DATABASE_URL environment variable is a variable that can be provided to db-migrate. If you provide this variable, you can omit using a database.json config file. (It’s not documented very well in the docs).