You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there's the setting keep_releases but on my laravel queue worker setup, for jobs that run a long time (days sometimes, yes), the deploys in-between can remove the code the worker was started with. This results in an error like include(/var/www/.../releases/42/vendor/composer/../../app/file.php) not found because folder 42 was already deleted.
Could there be an option to keep releases around for (eg) x days, or x seconds or whatever, which i can set to the maximum that i know my jobs will run at?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
Currently there's the setting
keep_releasesbut on my laravel queue worker setup, for jobs that run a long time (days sometimes, yes), the deploys in-between can remove the code the worker was started with. This results in an error likeinclude(/var/www/.../releases/42/vendor/composer/../../app/file.php) not foundbecause folder 42 was already deleted.Could there be an option to keep releases around for (eg) x days, or x seconds or whatever, which i can set to the maximum that i know my jobs will run at?
Beta Was this translation helpful? Give feedback.
All reactions