claroline/migration-bundle

Claroline migration bundle

Monday, May 30, 2016
by claroline
Repository
4 Watchers
1 Stars
7,778 Installations

PHP
2 Dependents
0 Suggesters
8 Forks
1 Open issues
15 Versions
0 % Grown

The README.md

README

WARNING

DEVELOPMENT HAS MOVED TO claroline/Distribution. THIS REPOSITORY IS NO LONGER MAINTAINED., _(*1)

Doctrine Migrations integration bundle providing :, _(*2)

Generation of migration classes on a per bundle basis
Generation for multiple target platforms
API allowing to execute migrations programmaticaly

, _(*3)

Installation

Install the bundle with composer:, _(*4)

composer require claroline/migration-bundle

Then add the bundle to your application kernel:, _(*5)

// app/AppKernel.php
<?php

use Symfony\Component\HttpKernel\Kernel;

class AppKernel extends Kernel
{
    public function registerBundles()
    {
        $bundles = array(
            // ...
            new Claroline\MigrationBundle\ClarolineMigrationBundle(),
        );
    }

    // ...
}

Commands

You can generate migrations for a specific bundle using:, _(*6)

php app/console claroline:migration:generate AcmeFooBundle

This command will create migration classes for all the available platforms in the Migrations directory of the bundle., _(*7)

You can execute a migration using one of the following commands:, _(*8)

php app/console claroline:migration:upgrade AcmeFooBundle
php app/console claroline:migration:downgrade AcmeFooBundle

By default, both commands execute the nearest available migration version (relatively to the current/installed one), but you can specify another target using the --target option:, _(*9)

php app/console claroline:migration:downgrade AcmeFooBundle --target=20130101124512
php app/console claroline:migration:upgrade AcmeFooBundle --target=nearest
php app/console claroline:migration:upgrade AcmeFooBundle --target=farthest

where farthest means a full upgrade/downgrade., _(*10)

The following command displays the list of available versions for a bundle and highlights the current/installed one:, _(*11)

php app/console claroline:migration:version AcmeFooBundle

Finally, you can delete generated migration classes which are above the current version of a bundle using:, _(*12)

php app/console claroline:migration:discard AcmeFooBundle

This last command is useful if you intend to "merge" several migration classes generated during development into a single migration class. In such a case, the steps to follow would be:, _(*13)

# downgrading to the newest version you want to keep
php app/console claroline:migration:downgrade AcmeFooBundle --target=20130101124512
# deleting everything above that version
php app/console claroline:migration:discard AcmeFooBundle
# generating a new migration class
php app/console claroline:migration:generate AcmeFooBundle

API

The whole API is accessible through the migration manager class:, _(*14)

<?php

$bundle = $container->get('kernel')->getBundle('AcmeFooBundle');
$container->get('claroline.migration.manager')->upgradeBundle($bundle, '20131201134501');

The Versions

30/05 2016

dev-master

9999999-dev http://www.claroline.net

Claroline migration bundle

bundle migration-bundle

Claroline migration bundle

claroline/migration-bundle

The README.md

README

WARNING

Installation

Commands

API

The Versions

dev-master

The Requires

The Development Requires

by Claroline development team

6.0.4

The Requires

The Development Requires

by Claroline development team

6.0.3

The Requires

The Development Requires

by Claroline development team

6.0.2

The Requires

The Development Requires

by Claroline development team

6.0.1

The Requires

The Development Requires

by Claroline development team

6.0.0

The Requires

The Development Requires

by Claroline development team

dev-5.x-stable

The Requires

The Development Requires

by Claroline development team

5.0.0

The Requires

The Development Requires

by Claroline development team

2.0.3

The Requires

The Development Requires

by Claroline development team

2.0.2

The Requires

The Development Requires

by Claroline development team

2.0.1

The Requires

The Development Requires

by Claroline development team

2.0.0

The Requires

The Development Requires

by Claroline development team

1.0.2

The Requires

The Development Requires

by Claroline development team

1.0.1

The Requires

The Development Requires

by Claroline development team

1.0.0

The Requires

The Development Requires

by Claroline development team