Fix ownership for /start-flower script in production Dockerfile #4603
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.
Description
Fixing a bug which seems like a missing a small typo. I needed to apply these changes to production env to be able to start Flower
Checklist:
The documentation doesn't need to be updated but I don't know how to test such change (it works on production tho)
Rationale
Fix #4602
This project is optionally shipped with Flower which doesn't run in production without this change. This seems like a small typo as other files are changing ownership to Django user. I hope I'm not missing something.
Thanks for a great project BTW ❤️
EDIT: I could add some small test suite for Flower if requested (just need more time) 🤞🏿