Pass parent environment into all child processes #106
Closed
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.
Explicitly copies the initial environment from the Cluster into the Sentinel and all worker processes.
Fixes #105
When deployed on AWS Elastic Beanstalk under supervisord the cluster's child worker processes did not have the same environment variables that were originally injected in the supervisord.conf. As a result the workers (presumably) didn't have access to
DJANGO_SETTINGS_MODULE
and couldn't locate the target task function, causingNo module named foo.tasks
errors.Explicitly passing the parent environment into each child process resolved this issue.
Solution based on:
http://stackoverflow.com/a/24664312