Download the PHP package mtoolkit/mtoolkit-evolutions without Composer

On this page you can find all versions of the php package mtoolkit/mtoolkit-evolutions. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of mtoolkit/mtoolkit-evolutions

Informations about the package mtoolkit-evolutions

MToolkit - Evolution

Agile way to manage your database releases.

Why

In the agile world you have to deploy quickly the new implementations of the software. Tracking and managing the changes of the database is difficult and boring. MToolkit - Evolution tries to make this task easy. We have been inspired by Play Framework: https://www.playframework.com/documentation/2.0/Evolutions You can track the database evolutions in your project (in a dedicated folder) and you can apply them for the release.

How to use

In your project, create one or more (one per each environment) .ini file like this:

This file will be used to connect to the database where you apply or revert the evolutions.

In a folder put the evolutions files. The names of the files must be 1.sql, 2.sql, etc. The content of the files must be like this:

UP and DOWN placeholders are mandatory. The UP queries will execute when you apply the evolutions. The DOWN queries will execute when you revert the evolutions.

Init

To initializate the database and before applying new evolutions, run the command:

Apply evolutions

To apply the evolutions run:

Revert evolutions

To revert the evolutions run:

To revert to a specific evolution use "-to=" argument:

The "down" query "1" will be executed.

Create PHAR executable

MToolkit Evolution uses box-project to create the PHAR file.

To create the PHAR executable, run the following command in the root of the project:

Not supported

All versions of mtoolkit-evolutions with dependencies

PHP Build Version
Package Version
Requires php Version >=5.5.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package mtoolkit/mtoolkit-evolutions contains the following files

Loading the files please wait ....