[Simplification] Remove Content Proxy as not needed reference#176
Merged
[Simplification] Remove Content Proxy as not needed reference#176
Conversation
vinaysrao1
approved these changes
Apr 5, 2026
Contributor
vinaysrao1
left a comment
There was a problem hiding this comment.
Perhaps add a comment in .env.example for VITE_CONTENT_PROXY_URL
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.
Context & Requests for Reviewers
As discussed the content proxy was a reference code on how to create a proxy for content, but this is not something we want to maintain as any content proxy deployment would work for this purpose. Users can still provide their own content proxy for iframe content and is configured via
VITE_CONTENT_PROXY_URLfor coop to use.