Celery fix#51
Merged
Merged
Conversation
alexhambley
approved these changes
May 16, 2025
Contributor
alexhambley
left a comment
alexhambley
left a comment
There was a problem hiding this comment.
Tested and all good!
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I've added the celery command back into the development docker compose - I guess I accidentally deleted this before.
I've also added the MINIO bucket name to the docker compose environment list. Because the docker build process is no longer loading all of the current directory into the container, the .env file that was caught in that process wasn't lost, and this was the only way that the bucket name was being provided. Now we are explicitly naming it in the docker compose it should work.