[2.0] Set the Horizon environment via command option #523
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
With this option we also can manage witch job run on different servers. |
driesvints
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The reasoning for this is because we use Envoyer to deploy our application to all machines (including workers) and use config caching to speed up the boot times of the workers.
By allowing a separated config option for setting the environment (
horizon.env) doesn't work for us since we have all web nodes also run a light version of the worker and have our worker servers run many processes for the heavy lifting and thus need to differentiate which because of config caching we can't do with .env vars.Long story short, this allows us to run
php artisan horizon --environment=workerin our supervisor config on the worker servers.