Ghost/MigratorConfig.js

var config = require('./core/server/config'),
    utils = require('./core/server/utils');

module.exports = {
    currentVersion: utils.ghostVersion.safe,
    database: config.get('database'),
    migrationPath: config.get('paths:migrationPath')
};
✨ knex-migrator v2 (#7605) * 🎨 knex-migrator reset [ci skip] * ✨ add migration example - hooks - 1.0 [ci skip] * 🛠 knex-migrator tarball - remove when released [ci skip] * 🎨 jscs/jshint * 🕵🏻 do not drop the database connection when running tests - please read the comments in the commit * 🔥 remove example migration * 🛠 knex-migrator 0.1.0 * 🛠 knex-migrator 0.1.1 - fix a single test to ensure we catch the error * 🛠 knex-migrator 0.1.2 * 🎨 make tests green - added my keyword: kate-migrations - i will go over all TODO's when removing the old migrations code * 🛠 knex-migrator update * 🛠 knex-migrator 0.2.0 2016-11-07 12:39:49 +01:00			`var config = require('./core/server/config'),`
🔥 remove database version (#7894) refs #7489 - as we are now using a different migration approach (knex-migrator), we don't need to remember the database version anymore - it was once used to check the state of a database and based on it we decided to migrate or not - with knex-migrator everything depends on the migration table entries and the current ghost version you are on - on current master the leftover usage is to add the db version when exporting the database, which can be replaced by reading the ghost version - removing this solves also an interesting migration case with knex-migrator: - you are on 1.0 - you update to 1.1, but 1.1 has no migrations - the db version would remain in 1.0 - because the db version was only updated when knex migrator executed a migration 2017-01-26 13:12:00 +01:00			`utils = require('./core/server/utils');`
✨ knex migrator (#7565) refs #7489 - remove sephiroth - use knex migrator npm - goodbye bootup script - 🎨 update README - 🎨 knex migrator @ 0.0.2 2016-10-17 14:50:29 +02:00
			`module.exports = {`
🔥 remove database version (#7894) refs #7489 - as we are now using a different migration approach (knex-migrator), we don't need to remember the database version anymore - it was once used to check the state of a database and based on it we decided to migrate or not - with knex-migrator everything depends on the migration table entries and the current ghost version you are on - on current master the leftover usage is to add the db version when exporting the database, which can be replaced by reading the ghost version - removing this solves also an interesting migration case with knex-migrator: - you are on 1.0 - you update to 1.1, but 1.1 has no migrations - the db version would remain in 1.0 - because the db version was only updated when knex migrator executed a migration 2017-01-26 13:12:00 +01:00			`currentVersion: utils.ghostVersion.safe,`
✨ knex migrator (#7565) refs #7489 - remove sephiroth - use knex migrator npm - goodbye bootup script - 🎨 update README - 🎨 knex migrator @ 0.0.2 2016-10-17 14:50:29 +02:00			`database: config.get('database'),`
			`migrationPath: config.get('paths:migrationPath')`
🛠 knex-migrator 1.0.0 (#7873) refs #7489 Most important change is the naming of the knex-migrator config file. 2017-01-23 12:32:17 +01:00			`};`