Skip to content

Conversation

@naglepuff
Copy link
Collaborator

I came across a couple of issues when setting up native development.

1. Unable to run docker compose with base compose file

The flower service defined in docker-compose.yml is dependent on celery, which itself is defined in docker-compose.override.yml. This led to errors when running docker compose -f ./docker-compose.yml up -d as per the native development instructions in the README. This PR moves flower into the override file.

2. Unable to access minio from local django server

While following along with the "native development" instructions in the README, I was unable to access minio from django, since django was attempting to reach it at minio:9000. I found that the service was actually reachable at localhost:9000, hence the change to .env.docker-compose-native.

Now it is in the same file as the service it depends on, and the main
compose file (docker-compose.yml) can be run by itself.
@naglepuff naglepuff requested a review from BryonLewis February 19, 2025 23:09
Copy link
Collaborator

@BryonLewis BryonLewis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a comment to fully remove 'flower' from the system it isn't needed. You can leave it as is if you want as well. The PR I'm working on removes flower from the system.

@naglepuff naglepuff merged commit cd9daa1 into main Feb 20, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants