- Looking at our Environment Variables, I have
- This means it executes this script for non-local environments: docker-php/50-laravel-automations at main · serversideup/docker-php · GitHub
These automations include:
Cache management(commented out due to a Laravel Bug with Rate Limiting)
- Database migrations (
php artisan migrate --force)
- Storage linking (
php artisan storage:link)
At first, I thought I was helping the user out by automating database migrations. As I looked into scaling containers, having this run on every container update could cause more issues than anything. Sometimes users may want it, but the I don’t think it is a smart engineering .
- If I change the default behavior to disable the automatons, I need to communicate this out to users since they will automatically receive image updates and probably wonder why their database migrations are no longer running
- Should database migrations (
php artisan migrate --force) default to NOT running automatically?
- Does storage linking (
php artisan storage:link) need to run all of the time (on a new container initialization)?