fix(uwsgi): add static-map for static files and user-media uploads#372
Merged
fix(uwsgi): add static-map for static files and user-media uploads#372
Conversation
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
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.
Summary
--static-mapdirectives to the Fargate entrypoint for/static/and/user-media/pathsChanges
docker/docker-entrypoint.sh--static-map=/staticand--static-map=/user-mediatostart_web()uWSGI commandWhy
The legacy EC2 setup uses
olympia.iniwithstatic-mapdirectives to serve static files and user-uploaded media directly from uWSGI. Our Fargate entrypoint did not carry these over, resulting in 404s for all/static/and/user-media/paths.Reference:
thundernest-ansible/addons/olympia.inilines 55-56.Validation
static-mappaths match the Ansible config/static/maps to/data/olympia/site-static/(built into the Docker image)/user-media/maps to$NETAPP_STORAGE_ROOT/shared_storage/uploads/(falls back to/tmp/storagewhen EFS is not mounted)Safety
No impact on running services until the new image is deployed. Static file serving is read-only by nature.
Follow-up
EFS mount targets and task definition volumes for persistent user-media storage will be addressed in a separate infrastructure PR.