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.
Problem:
Celery workers don't have auto reloading and getting latest changes for a worker tends to be a tricky and painstaking process. Current methods of development include running the worker locally in venv or calling down/up on the compose file for every code change.
Solution:
By mounting the code volume into the discovery container, we can propagate the latest code changes into the container. Then we can call
docker restart <container-id>
to trigger the new code to be run on restart.Testing:
I tested this locally by adding a log in the index.py flow
I then ran discovery worker and made sure it printed out in the logs. I then changed the log message and called the docker restart command and verified the new message showed up in the logs.