Replies: 1 comment 3 replies
-
|
The system status is used for more than just deployments. We are planning on repurposing Craft’s “Maintenance Mode” in Craft 5 to be used for deployments (#9855), at which point it would make sense to pause queue execution as well. |
Beta Was this translation helpful? Give feedback.
-
|
Then how about introducing a new variable like There may still be pretty of time before Craft 5 is released ... last time I had 3 failed deployments in a row until I manually deactivated the queue-job. |
Beta Was this translation helpful? Give feedback.
-
|
How exactly are you running your queue? |
Beta Was this translation helpful? Give feedback.
-
|
As cron-job (accordingly to https://github.com/yiisoft/yii2-queue/blob/master/docs/guide/worker.md#cron): |
Beta Was this translation helpful? Give feedback.
-
We are having issues during deployment because of the queue-worker which locks database-tables or is writing logfiles. Therefore I suggest that if isSystemLive / CRAFT_IS_SYSTEM_LIVE is set to false:
This should be applied for queue/run (cronjob) as well as queue/listen (daemon). So that after the deployment updates applied to the queue-handling itself are activated with the first start of the queue after the deployment.
Beta Was this translation helpful? Give feedback.
All reactions