Update README to include more info about deploying #168
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
Hi, I've reorganized the section about deploying the frontend service for clarity. I also added a note about deploying both the WordPress service and the frontend to a cloud platform, including a link to my guide for doing this on GCP. I think it would be great to take the markup from that post + other potential future guides to deploying just the guide frontend to zeit, or the whole thing to elastic beanstalk, or even Kubernetes, and organize them as part of this project's documentation. Seems like it would save people time / frustration!
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.
Hi, I've reorganized the section about deploying the frontend service for clarity.
I also added a note about deploying both the WordPress service and the frontend to cloud platforms, including a link to my guide for doing this on GCP.
I think it would be great to take the markup from my guide + other potential future guides to deploying just the frontend to zeit, or the whole thing to elastic beanstalk, or even Kubernetes, and organize them as part of this project's documentation.
Seems like it would save people time / frustration and fits under the "starter kit" scope of this project!