Allow Gatbsy to redirect v1 pages to v2 pages #612
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
EyeOfPython
pushed a commit
to EyeOfPython/bitcoincash.org
that referenced
this pull request
Nov 17, 2020
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 effectively does not route v1 content anymore except for the remaining pages which are not yet v2-complete.
This will allow Gatsby to determine v1 -> v2 redirects.
This change will not disrupt any deployments for v2 content, but in order for v1 to correctly redirect to v2 for the remaining pages, the associated block in nginx.conf will need to removed for that redirect to work correctly. This should only be done
once the v2 page has baked in prod and is considered stable.
Depends on #611