feat: fallback to remote for assets #18
Open
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.
This pull request introduces a new mechanism for handling asset uploads in a multisite WordPress setup. The main changes enable the application to redirect requests for missing files in the
app/uploadsdirectory to a remote asset server, improving asset availability and simplifying development workflows.Remote asset handling:
LANDO_REMOTE_ASSETS_URLenvironment variable to.lando.brave.ymlto specify the remote asset server for use in local development.Nginx configuration updates:
provision/nginx/multisite-subdomain-subdirectory.confto add a new location block for/app/uploads/. If a requested file does not exist locally, requests are redirected to the remote asset server using the value ofLANDO_REMOTE_ASSETS_URL.