Still trying to figure out what the cause is, but right now, almost every deployment triggers a 503. This can be resolved by an artisan optimize:clear or similar cache-dropping methods.
Right now, we have a hotfix in place where a cron checks the site for a 503, and if so, fires the command.
DavidLambauer
commented
1 year ago
Still trying to figure out what the cause is, but right now, almost every deployment triggers a 503. This can be resolved by an
artisan optimize:clearor similar cache-dropping methods.Right now, we have a hotfix in place where a cron checks the site for a 503, and if so, fires the command.
This ticket is for documentation purposes...