Docsify publishing with AWS Amplify steps #792
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
This is to help users be able to publish Docsify with AWS Amplify, so they don't get stuck on redirect rules and hash state issues.
jthegedus
approved these changes
Mar 15, 2019
|
@timaschew I would merge if I could! |
Thanks @jthegedus. |
|
@gemmadlou did you every have any issue with files in the _media folder being not found? I followed your instructions (thank you for these!) and I can't seem to get the page to load with the media assets |
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 is to help users to be able to publish Docsify with AWS Amplify, so they don't get stuck on redirect rules and hash state issues.
Please makes sure these boxes are checked before submitting your PR, thank you!
masterbranch.libdirectory.