Download the PHP package dreadlabs/app-migration without Composer
On this page you can find all versions of the php package dreadlabs/app-migration. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download dreadlabs/app-migration
More information about dreadlabs/app-migration
Files in dreadlabs/app-migration
Package app-migration
Short Description Provides a package for adding runtime migrations to an application.
License MIT
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 app-migration
AppMigration
Provides an opinionated, ready-to-use way to integrate runtime migration into your PHP application.
Status
Installation
~ $ php composer.phar require dreadlabs/app-migration:~0.1.1Components
Interfaces
- LockInterface - Adapter interface to locking library
- LoggerInterface - An slimmed down version of the PSR-3 logger interface
- MediatorInterface - This is the glue between lock, logger and migrator
- MigratorInterface -Adapter interface to migration library
Exceptions
- LockingException - If anything goes wrong during locking
- MigrationException - If a migration can't be executed. Exception code is the version number of the migration which produced the exception.
- TopologyViolationException - If one or more unprocessed migrations are younger than the latest processed migration.
Companion packages
- dreadlabs/app-migration-lock-ninjamutex - A lock adapter for
arvenil/ninja-mutex - dreadlabs/app-migration-migrator-phinx - A migrator adapter for
robmorgan/phinx - dreadlabs/app-migration-typo3 - An integration into TYPO3.CMS
Opinionated - why?
Topological assumption
I believe, there should be only one direction during migration: "up". This belief comes from looking to migrations like they are ordered on a time axis. You can't go back in time - can you? - and therefore no way to migrate "down".
If you have the need to migrate down (e.g. during testing), just create another migration which rolls back the last one. Then decide which migrations to drop and which can go into CVS.
Logging
Logging is essential during migration. If something went wrong, you need to know as soon as possible what is the problem. Logging is a first class citizen in the mediator. If you don't need logging, just pass in a NullLogger and you're good to go.
License
MIT, © 2015 Thomas Juhnke
