Download the PHP package gatherdigital/pimcore-migrations without Composer

On this page you can find all versions of the php package gatherdigital/pimcore-migrations. 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 pimcore-migrations

Pimcore Migrations Plugin

Introduction

Pimcore already does a lot of migration work for developers, all class definition changes and database schema changes can be easily ported between development, staging and production environments. However, the following use-cases for database changes are not easily portable between Pimcore environments:

What this plugin provides

This plugin provides a simple mechanism for implementing version controllable database changes between pimcore environments, in a lightweight convention similar to packages such as Phinx or Doctrine Migrations.

Installation

Install using composer:

Configuration

Configuration is intended to be as simple as possible.

  1. After install ensure that the extensionis listed as follows in your extensions.php file

  2. Migrations should be placed in your /website/var/plugins/PimcoreMigrations/migrations folder.

  3. The plugin will automatically install a new table into the pimcore environment upon detecting a migrations folder when the console app is executed.

Usage

Extend the AbstractMigration Class

  1. Each migration should extend the class PimcoreMigrations\Model\AbstractMigration.
  2. It can be named however you wish, although the last part of the name should be a numeric value separated by an underscore (_). For example:
    • some_table_changes_1000.php
    • new_custom_persistent_class_1001.php
    • anotherdifferentlynamedclass_1002.php
  3. Each migration class should have a similarly named classname following the same pattern as Pimcore, example:
    • SomeTableChanges1000
    • NewCustomPersistentClass1001
    • Anotherdifferentlynamedclass1002
  4. If we created the classes above we would have the following versions (represented by an integer)
    • 1000
    • 1001
    • 1002

Implement the required class methods

Each Migration should contain both an up() and down() method. UP being the default operation, and DOWN being to roll back changes. Here is an example:

Run the console app

Migrations can be run through the console application made available in the Pimcore\Cli. Running as a plugin ensures that all migrations are runnning in the Pimcore environment. There are 3 commands available and can be run as follows:

  1. Check Status

  2. Migrate up

  3. Migrate down

Use Case Example

One of our biggest concerns is keeping development, staging and production environments intact whilst there are many changes happening within the database between the development team. Pimcore Migrations features a method that allows us to keep classdefinitions in sync whilst providing a little bit of integrity checking / feedback. A typical starting migration for our projects may be as follows:


All versions of pimcore-migrations with dependencies

PHP Build Version
Package Version
Requires php Version >=5.6.0
pimcore/installer-plugin Version ~1.3
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 gatherdigital/pimcore-migrations contains the following files

Loading the files please wait ....