Download the PHP package jeremygiberson/doctrine-migrations-boilerplate without Composer

On this page you can find all versions of the php package jeremygiberson/doctrine-migrations-boilerplate. 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?

Informations about the package doctrine-migrations-boilerplate

Migrations Boilerplate

This project wires up Doctrine ORM & Migrations.

The project contains a working ORM + Migrations wiring/configuration. It's not a statement of best practices or anything, just a working example to get you going. Feel free to change things to your preference needs.

In order to use the command line tools you need to create the Entity Manager and provide the configuration to your model/mapping paths. But you'll also need the same configuration to create the Entity Manager in your application code. Rather than put this configuration in your application configuration or bootstrap, it's a good idea to keep entity manager & ORM configuration in a separate tiny config file. This lets you reuse the config in your app bootstrap and your command line config (and or test suite configs) without having to bootstrap your app config. This is just a suggestion though and you don't have to follow it.

Installation

Use composer to create a new project based off this boilerplate.

Overrides

See doctrine-config.php.dist for overridable values. To override, copy the file to doctrine-config.php and change values to match your requirements.

Usage

Status

Check migrations status

vendor/bin/doctrine-migrations migrations:status

Migrate

Run pending migrations

vendor/bin/doctrine-migrations migrations:migrate

Diff

Generate a migration file by comparing current schema to your model definitions.

vendor/bin/doctrine-migrations migrations:diff

Other Commands

There are other commands available. You can see the list by running doctrine-migration without arguments.

vendor/bin/doctrine-migrations

All versions of doctrine-migrations-boilerplate with dependencies

PHP Build Version
Package Version
Requires doctrine/orm Version ^2.5
doctrine/migrations Version ^1.4
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 jeremygiberson/doctrine-migrations-boilerplate contains the following files

Loading the files please wait ....