Proxy the Effection and Graphgen sites directly #323
Merged
Conversation
This file contains 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
Cut Netlify out of the loop. Right now, when someone asks for https://frontside.com/effection The request proceeds from 1. frontside.deno.com 2. frontside.netlify.app 3. effection.deno.com And the response comes back via 3. effection.deno.com 2. frontside.netlify.app 1. frontside.deno.com Eventually we want to be able to serve all the code directly from frontside.deno.com, and the first stem is to cut out netlify completely from that round trip. This removes the netilfy redirects for graphgen, and effection, and adds them directly to the frontside.com site.
✅ Deploy Preview for frontside canceled.
|
elrickvm
approved these changes
Nov 7, 2023
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.
Motivation
Cut Netlify out of the loop.
Right now, when someone asks for https://frontside.com/effection
The request proceeds from
And the response comes back via
Eventually we want to be able to serve all the code directly from frontside.deno.com, and the first stem is to cut out netlify completely from that round trip.
Approach
This removes the netilfy redirects for graphgen, and effection, and adds them directly to the frontside.com site.
Preview
https://frontside--directly-redirect-to-effec.deno.dev/graphgen