nginx recursive content routing for non-production environments #4855
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
/content
reverse proxyValue add
develop-studio-content
) every time we restore a database. Furthermore, this saves us a ton money because we no longer have to replicate storage files from the production bucket.References
Discussion https://learningequality.slack.com/archives/C0WHZ9FPX/p1733344134300819
Reviewer guidance
/etc/hosts
and setminio
to resolve to your machine (this is an unaddressed caveat with running everything through docker-- the internal API needs to use the docker network hostname)docker-compose build
docker-compose up
localhost:8081
. A real example, http://localhost:8081/content/storage/0/d/0d66e3e3c85faf413bc0033dcb6510ce.pdflocalhost:8081
. A real example, http://localhost:8081/content/storage/b/b/bbfad3ef03bc1e08d3c31ad8052ee5b5.pdflocalhost:8081
Post-merge followup
When this is merged, we can proceed with cleaning things up:
hotfixes
andunstable