This PR introduces Bowler configuration file, that you may optionally publish to your app configuration directory. You no longer need to manually dump stuff into your config/queue.php file.
The changes were motivated by #49 were we introduced lifecycle hooks. We decided to suppress errors that are thrown from a registered callback by default, however it doesn't seem very nice to force users into this behavior. Instead, we'd like to offer them a choice how to handle errors which sparked the idea of config management.
Note that this is a technically a breaking change. The new configuration assumes the following env variables:
This PR introduces Bowler configuration file, that you may optionally publish to your app configuration directory. You no longer need to manually dump stuff into your
config/queue.phpfile.The changes were motivated by #49 were we introduced lifecycle hooks. We decided to suppress errors that are thrown from a registered callback by default, however it doesn't seem very nice to force users into this behavior. Instead, we'd like to offer them a choice how to handle errors which sparked the idea of config management.
Note that this is a technically a breaking change. The new configuration assumes the following env variables:
The PR includes changes to #49, however you should consider reviewing them separately. See commit https://github.com/Vinelab/bowler/pull/50/commits/1b036e44b740348b44e4adc1c8daec126b28b045