Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/vorban/migration-disorder-bug-report
Showcasing migration publishing disorder in Laravel.
https://github.com/vorban/migration-disorder-bug-report
Last synced: about 2 months ago
JSON representation
Showcasing migration publishing disorder in Laravel.
- Host: GitHub
- URL: https://github.com/vorban/migration-disorder-bug-report
- Owner: vorban
- Created: 2024-07-09T20:00:56.000Z (7 months ago)
- Default Branch: main
- Last Pushed: 2024-07-09T20:28:45.000Z (7 months ago)
- Last Synced: 2024-07-10T00:58:04.669Z (7 months ago)
- Language: PHP
- Size: 211 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Migration disorder bug report
When publishing migrations, they are created
in a random order that does not reflect the
intented ordering.
## Quick tour
The laravel app is brand new and generated with `laravel new`.
The only change is the addition of the path repository in `composer.json`
for the package that publishes migrations, along with the composer requirement for that package.
The `./disorder` directory is a package that publishes 3 classic migrations.
They are naturally ordered via valid timestamps. Those are expected to be updated
by laravel during publishing.
Migrations `create_api_keys_table` and `seed_default_customer` both depend on `create_customers_table`,
so running them out of order will fail.
## Installing and trying out
```sh
git clone [email protected]:vorban/migration-disorder-bug-report.git
cd migration-disorder-bug-report
composer install
artisan vendor:publish --tag=disorder
```
The outcome is seemingly random. Here is a screenshot of one attempt that I got:
