Download the PHP package studioemma/system-migrations-bundle without Composer
On this page you can find all versions of the php package studioemma/system-migrations-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
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 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.
Informations about the package system-migrations-bundle
Pimcore System Migrations Bundle
This bundle allows to run system database migrations independent from the Pimcore 5 code updates. This is particulary usefull when you do a full update in a development environment and have to just replay the database migrations on your other environments like staging and production.
The problem
Pimcore 5 allows you to update your installation via commandline or via the admin web interface. But these updates are both code and database migrations. So in the case that you are doing your update in a development environment to prepare everything for the next update in staging and production these steps are not reproducable. The code will be updated due to a deploy on your other environment, but the database migrations will not be there, potentially causing all sorts of issues and/or unexpected behaviour.
Pimcore 5.4.0
As of pimcore 5.4.0 you will have to run the CoreBundle migrations to get this functionality.
When you are updating from a lower version than 5.4.0, first update to the latest 5.3.x and then remove this bundle when updating to 5.4.0.
Installation
This will create an extra table plugin_se_system_migrations where the build
and updatedate are tracked. Initially after install it will contain 1 record
containing the current Pimcore 5 build number and the date of installation.
Usage
Running this will determine based on the plugin_se_system_migrations table
and the build number found in Version.php what must be done. It will upgrade
the database or downgrade the database - if possible - to the schema version
associated with the current version of your Pimcore 5 code.
When you install this plugin in an existing installation you can also
re-initialize the plugin_se_system_migrations table - say you have installed
this plugin in dev, but prod is not yet updated.
This command will reset the plugin_se_system_migrations table and insert only
one record with the chosen buildnumber and the current date.
Versioning
Since the easiest and most comprehensible way of versioning was to take the major version as the pimcore build number we do not follow semver. If you want to be able to fully use this bundle you should use the latest version. It is limited to Pimcore 5. If there is a Pimcore 6 release this bundle could be updated or become obsolete.
License
GPLv3. See License file for more information
