PHPackages oxid-esales/eshop-doctrine-migration-wrapper - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Database & ORM](/categories/database) 4. / 5. oxid-esales/eshop-doctrine-migration-wrapper ActiveLibrary[Database & ORM](/categories/database) oxid-esales/eshop-doctrine-migration-wrapper ============================================ OXID eShop database migrations using doctrine v1.0.1(9y ago)013.1k1GPL-3.0Shell Since Oct 27Pushed 7y ago15 watchersCompare [ Source](https://github.com/OXID-eSales/eshop-doctrine_migration_wrapper)[ Packagist](https://packagist.org/packages/oxid-esales/eshop-doctrine-migration-wrapper)[ RSS](/packages/oxid-esales-eshop-doctrine-migration-wrapper/feed)WikiDiscussions master Synced 4w ago READMEChangelog (2)Dependencies (2)Versions (4)Used By (1) OXID eShop doctrine migration integration ----------------------------------------- [](#oxid-eshop-doctrine-migration-integration) Current component allows to execute **doctrine migration binary** for active eShop edition and with database configured from the eShop installation itself. The following different logic is applied during the execution of different migration scripts suites within different eShop editions: - **Community edition migrations** - executed always; - **Professional edition migrations** - executed when eShop has Professional edition or Enterprise edition; - **Enterprise edition migrations** - executed when eShop has Enterprise edition; - **Project specific migrations** - executed always; Keep in mind that the migration suite is executed only when it is able to find **at least one** migration script. This component relies on information provided by [eshop-edition\_facts](https://github.com/OXID-eSales/eshop-edition_facts)component in order to determine the current eShop installation edition. This fact is taken from `ESHOP_EDITION` environment variable. In order to bypass the above described logic and execute **only one specific migration script suite** the environment variable `MIGRATION_SUITE`must not be empty! e.g. to execute only Enterprise edition migration script suite use the following: `MIGRATION_SUITE=EE ./vendor/bin/oe-eshop-facts oe-eshop-doctrine_migration` The main script `oe-eshop-doctrine_migration` forwards all provided argument values to the doctrine migration tool CLI. Here are few basic examples: - `./vendor/bin/oe-eshop-facts oe-eshop-doctrine_migration` - Lists all available commands; - `./vendor/bin/oe-eshop-facts oe-eshop-doctrine_migration migrations:execute`- execute migrations; - `./vendor/bin/oe-eshop-facts oe-eshop-doctrine_migration migrations:generate`- generate new migration; (It's advised to use this together with `MIGRATION_SUITE` environment variable to ensure that only one migration suite will be populated with new migration script) More information about **doctrine migration component** and it's CLI usage can be found on their [documentation page](http://docs.doctrine-project.org/projects/doctrine-migrations/en/latest/toc.html). OXID eShop doctrine migration integration related facts ------------------------------------------------------- [](#oxid-eshop-doctrine-migration-integration-related-facts) This component provides eShop doctrine migration integration facts with the help of [eshop-facts](https://github.com/OXID-eSales/eshop-facts). Information on how to use `oe-eshop-doctrine_migration_facts` script together with `oe-eshop-facts` can be found in the following [README](https://github.com/OXID-eSales/eshop-facts/blob/master/README.rst). ### Output [](#output) The following information is provided after executing the script: - `ESHOP_DOCTRINE_MIGRATION_WRAPPER_VENDOR_PATH` - Full path to current scripts directory; - `ESHOP_DOCTRINE_MIGRATION_BIN_PATH` - Full path to 3rd party component's doctrine-migrations binary file; - `ESHOP_DOCTRINE_CONFIG_FILENAME` - Filename used for migration configuration; - `ESHOP_DOCTRINE_DB_CONFIG_FILENAME` - Filename used for database migration configuration; - `ESHOP_DOCTRINE_CE_MIGRATION_CONFIG_PATH` - Full path to eShop CE migration configuration file; - `ESHOP_DOCTRINE_CE_MIGRATION_DATA_PATH` - Full path to eShop CE migration files directory; - `ESHOP_DOCTRINE_CE_MIGRATION_DB_CONFIG_PATH` - Full path to eShop CE database migration configuration file; - `ESHOP_DOCTRINE_CE_HAS_MIGRATIONS` - "1" is given in case eShop CE has valid migration files present; - `ESHOP_DOCTRINE_PE_MIGRATION_CONFIG_PATH` - Full path to eShop PE migration configuration file; - `ESHOP_DOCTRINE_PE_MIGRATION_DATA_PATH` - Full path to eShop PE migration files directory; - `ESHOP_DOCTRINE_PE_MIGRATION_DB_CONFIG_PATH` - Full path to eShop PE database migration configuration file; - `ESHOP_DOCTRINE_PE_HAS_MIGRATIONS` - "1" is given in case eShop PE has valid migration files present; - `ESHOP_DOCTRINE_EE_MIGRATION_CONFIG_PATH` - Full path to eShop EE migration configuration file; - `ESHOP_DOCTRINE_EE_MIGRATION_DATA_PATH` - Full path to eShop EE migration files directory; - `ESHOP_DOCTRINE_EE_MIGRATION_DB_CONFIG_PATH` - Full path to eShop EE database migration configuration file; - `ESHOP_DOCTRINE_EE_HAS_MIGRATIONS` - "1" is given in case eShop EE has valid migration files present; - `ESHOP_DOCTRINE_PROJECT_MIGRATION_CONFIG_PATH` - Full path to eShop project migration configuration file; - `ESHOP_DOCTRINE_PROJECT_MIGRATION_DATA_PATH` - Full path to eShop project migration files directory; - `ESHOP_DOCTRINE_PROJECT_MIGRATION_DB_CONFIG_PATH` - Full path to eShop project database migration configuration file; - `ESHOP_DOCTRINE_PROJECT_HAS_MIGRATIONS` - "1" is given in case eShop project has valid migration files present. Keep in mind that it's possible to override any variable from the list above by providing it as an environment variable, e.g. to change the doctrine migration binary path: `ESHOP_DOCTRINE_MIGRATION_BIN_PATH=/usr/local/bin/doctrine-migration ./vendor/bin/oe-eshop-facts oe-eshop-doctrine_migration_facts` ### Input [](#input) The following environment variables are accepted: - `VERBOSE` - Enables verbose mode which prints out all facts to `STDOUT`; - `ESHOP_VERBOSE_DOCTRINE_MIGRATION_FACTS` - Enables verbose mode only for the current script. ### Health Score 33 — LowBetter than 72% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity21 Limited adoption so far Community17 Small or concentrated contributor base Maturity65 Established project with proven stability Bus Factor2 2 contributors hold 50%+ of commits How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~36 days Total 2 Last Release 3498d ago ### Community Maintainers ![](https://avatars.githubusercontent.com/u/1374817?v=4)[oxid](/maintainers/oxid)[@OxID](https://github.com/OxID) --- Top Contributors [![rezonanc-oxid](https://avatars.githubusercontent.com/u/8058763?v=4)](https://github.com/rezonanc-oxid "rezonanc-oxid (3 commits)")[![logiforge](https://avatars.githubusercontent.com/u/1391042?v=4)](https://github.com/logiforge "logiforge (2 commits)")[![tarique-iqbal](https://avatars.githubusercontent.com/u/1391042?v=4)](https://github.com/tarique-iqbal "tarique-iqbal (2 commits)")[![hkreuter](https://avatars.githubusercontent.com/u/3692295?v=4)](https://github.com/hkreuter "hkreuter (1 commits)") ### Embed Badge ![Health badge](/badges/oxid-esales-eshop-doctrine-migration-wrapper/health.svg) ``` [![Health](https://phpackages.com/badges/oxid-esales-eshop-doctrine-migration-wrapper/health.svg)](https://phpackages.com/packages/oxid-esales-eshop-doctrine-migration-wrapper) ``` ### Alternatives [doctrine/doctrine-migrations-bundle Symfony DoctrineMigrationsBundle 4.3k185.0M658](/packages/doctrine-doctrine-migrations-bundle)[sylius/sylius E-Commerce platform for PHP, based on Symfony framework. 8.5k5.9M719](/packages/sylius-sylius)[patchlevel/event-sourcing A lightweight but also all-inclusive event sourcing library with a focus on developer experience 207362.9k13](/packages/patchlevel-event-sourcing)[laravel-doctrine/migrations Doctrine Migrations for Laravel 792.9M17](/packages/laravel-doctrine-migrations)[sylius-labs/doctrine-migrations-extra-bundle 227.1M16](/packages/sylius-labs-doctrine-migrations-extra-bundle)[nettrine/migrations Doctrine Migrations for Nette Framework 421.8M20](/packages/nettrine-migrations) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)