-
-
Notifications
You must be signed in to change notification settings - Fork 332
fix: Running Migrations On Clean Installs #439
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes a bug where database migrations were running on clean Mautic installations, which could cause issues during the initial setup process. The fix adds a check to determine if Mautic is already installed before running migrations.
- Adds conditional logic to only run migrations when Mautic is already installed
- Introduces logging to track when migrations are run or skipped
- Uses the presence of
site_urlparameter in local.php as the installation indicator
|
@mautic/docker-maintainers could you please review this one? It's a blocker for 7.0.0-alpha |
Co-authored-by: Martin Vooremäe <martin.vooremae@gmail.com>
Co-authored-by: Martin Vooremäe <martin.vooremae@gmail.com>
|
Pipelines are going to fail. See #441 |
This PR fixes #437, which was a bug introduced on #434, when trying to improve the upgrading process of the image.
Now migrations should only be ran when the container detects that Mautic is already installed, meaning, when local.php contains
parameters['site_url']