[Docker] Blueprint doesn't run or check for database migrations

Someone wants to install the extension I made but for some reason the migration check is skipped. Installation doesn't show any errors, its just that the message INFO: Running database migrations... is missing. Blueprint beta-2024-12 is being used and I don't know if the official docker container/installation is being used. The screenshot shows the installing process where the migration check should be at the end. Any idea what I could do here?
No description
7 Replies
Emma
Emma•2mo ago
thats weird.. does running migrations manually work?
Sirzento | Nico
Sirzento | NicoOP•2mo ago
How can this be done?
Loki
Loki•5w ago
They should update Blueprint; it's automatic now. - Take a backup of the volume just in case - Go to the folder with the compose file - docker compose pull - docker compose down -v panel - docker compose down - docker compose up -d Wait 15 seconds - If they have the alias set up - blueprint -i *.blueprint - If they don't - docker compose exec panel blueprint -i *.blueprint
Sirzento | Nico
Sirzento | NicoOP•5w ago
But isn't that already the latest stable non preview version? 🤔 I mean it also should work with the 2024 version but somehow docker makes problems I guess?
Loki
Loki•5w ago
I didn't check. I just assumed it was a few versions behind, since I ran into an identical issue a while back. The choices to fix it were running migrations manually, updating Blueprint and reinstalling, or fixing the install script for the extension so it manually ran migrations just for the extension's path.
Sirzento | Nico
Sirzento | NicoOP•5w ago
So since Blueprint is already uptodate and "fixing" the install script shouldn't be an option because it would just be a workaround, manual running the migration would be the only option except from reinstall and hoping that it works after that. How can you manual run migrations? Never done this before
Loki
Loki•5w ago
You don't really have to put a specific path; it won't re-do stuff it already did. You can add --path as an argument and target specific extensions or specific migration files in those extensions, but I'm not very familiar with this; I'd backup the container and the database and just run migrations normally.
No description

Did you find this page helpful?