ghost/core/server/data/migration/fixtures/index.js

var populate = require('./populate'),
    update   = require('./update'),
    fixtures = require('./fixtures');

module.exports = {
    populate: populate,
    update: update,
    fixtures: fixtures
};
Refactor & test fixture migrations refs #6301 Fixtures: - Removed all the old (and now broken) 003 fixture upgrades - Split the 004 fixture upgrade tasks out, each into their own file - Improved the versioning code that figured out which upgrades we should do - Added lots of test coverage to make sure all the fixtures are still being run correctly. Permissions fixtures: - Changed the code that was populating permissions fixtures to be more automated & based only on what is in the permissions.json file. - Added lots of test coverage to make sure all the permissions are still being created correctly. Merging the two things: - Merged the content of permissions.json and fixtures.json into fixtures.json, but using the new structure from permissions.json. - Changed to use the new automated model & relation creation for all fixtures, not just permissions. - The only thing that can't be auto-populated just now is the owner creation, I think that's important enough to do separately. - There were (so far) never any permission updates, so code for updating fixtures stays the same through the merge. - This results in two clear code paths: populate (fill out a brand new DB) and update (make any changes since the last version) Test coverage is now 100% across both updates and populations. 2016-02-25 08:10:36 +01:00			`var populate = require('./populate'),`
			`update = require('./update'),`
			`fixtures = require('./fixtures');`
Refactoring fixtures refs #2600, refs #2379 Refactoring fixtures to make permission management a little easier - Separate fixtures into JSON file and split permissions fixtures from other fixtures - make fixture migrations more robust by fetching objects, not relying on ids and checking before adding - changed owner fixture slightly to remove any confusion between the 'Owner' role and 'Ghost Owner' user. - moved 003 fixture versions out of config into logic, possibly not a good idea - refactored permissions fixtures and added permissions_roles fixtures to make it easier to read / add 2014-07-11 08:12:07 +01:00
Add new permissions to fixtures closes #2325 - added new permissions - added relation to user roles - added updateFixtures to migrateUp - removed validation per model to fix tests 2014-03-14 18:36:45 +01:00			`module.exports = {`
Refactoring fixtures refs #2600, refs #2379 Refactoring fixtures to make permission management a little easier - Separate fixtures into JSON file and split permissions fixtures from other fixtures - make fixture migrations more robust by fetching objects, not relying on ids and checking before adding - changed owner fixture slightly to remove any confusion between the 'Owner' role and 'Ghost Owner' user. - moved 003 fixture versions out of config into logic, possibly not a good idea - refactored permissions fixtures and added permissions_roles fixtures to make it easier to read / add 2014-07-11 08:12:07 +01:00			`populate: populate,`
Refactor & test fixture migrations refs #6301 Fixtures: - Removed all the old (and now broken) 003 fixture upgrades - Split the 004 fixture upgrade tasks out, each into their own file - Improved the versioning code that figured out which upgrades we should do - Added lots of test coverage to make sure all the fixtures are still being run correctly. Permissions fixtures: - Changed the code that was populating permissions fixtures to be more automated & based only on what is in the permissions.json file. - Added lots of test coverage to make sure all the permissions are still being created correctly. Merging the two things: - Merged the content of permissions.json and fixtures.json into fixtures.json, but using the new structure from permissions.json. - Changed to use the new automated model & relation creation for all fixtures, not just permissions. - The only thing that can't be auto-populated just now is the owner creation, I think that's important enough to do separately. - There were (so far) never any permission updates, so code for updating fixtures stays the same through the merge. - This results in two clear code paths: populate (fill out a brand new DB) and update (make any changes since the last version) Test coverage is now 100% across both updates and populations. 2016-02-25 08:10:36 +01:00			`update: update,`
			`fixtures: fixtures`
Use current user in models closes #2058 - fixed apiContext as suggested in the issue - added user to options object for models - added api.users.register() for public registration - changed models to use options.user for created_by, updated_by, author_id and published_by - added override to session model to avoid created_by and updated_by values - added user (id: 1) to tests - added user (id: 1) for registration - added user (id: 1) for import, fixtures and default settings - added user (id: 1) for user update - added user (id: 1) for settings update (dbHash, installedApps, update check) - updated bookshelf to version 0.6.8 2014-04-03 15:03:09 +02:00			`};`