The CLI is more useful because it uses process.env.NODE_ENV to pick a key from knexfile.js to look for config.

Is it possible to disable this behavior? I'd prefer to manage my own configuration and environments and just use knexfile.js to export an appropriate configuration for the current environment.

So instead of this...

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

module.exports = {
    development: {
        client: config.databaseDialect,
        connection: {
            host: config.databaseHost,
            user: config.databaseUsername,
            password: config.databasePassword,
            database: config.databaseName
        },
        pool: {
            min: 2,
            max: 10
        },
        migrations: {
            tableName: 'schema_info'
        }
    },

    test: {
        client: config.databaseDialect,
        connection: {
            host: config.databaseHost,
            user: config.databaseUsername,
            password: config.databasePassword,
            database: config.databaseName
        },
        pool: {
            min: 2,
            max: 10
        },
        migrations: {
            tableName: 'schema_info'
        }
    },

    production: {
        client: config.databaseDialect,
        connection: {
            host: config.databaseHost,
            user: config.databaseUsername,
            password: config.databasePassword,
            database: config.databaseName
        },
        pool: {
            min: 2,
            max: 10
        },
        migrations: {
            tableName: 'schema_info'
        }
    }
};

... I'd prefer something like this:

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

module.exports = {
    client: config.databaseDialect,
    connection: {
        host: config.databaseHost,
        user: config.databaseUsername,
        password: config.databasePassword,
        database: config.databaseName
    },
    pool: {
        min: 2,
        max: 10
    },
    migrations: {
        tableName: 'schema_info'
    }
};

The only "advantage" to specifying configuration options for each environment that I can think of is migrating all databases in sync, though I don't want that behavior either. An argument in favor of the simpler syntax is that is what is used to establish the connection for my models. Why make it one way here and another way somewhere else?

Allow migrations to be used without environments #328

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions