From 61047c5ad1cbe93e8b0c3653f32949d45f711d44 Mon Sep 17 00:00:00 2001 From: Patrick Steadman Date: Thu, 20 Dec 2018 12:07:35 -0500 Subject: [PATCH 1/2] Update README to include more info about deploying 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! --- README.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 7fe8dcbd..9a8bb941 100644 --- a/README.md +++ b/README.md @@ -66,11 +66,9 @@ To spin up the frontend client app, run the following commands: The Next.js app will be running on [http://localhost:3000](http://localhost:3000). -### Docker +### Deploying -Most WordPress hosts don't also host Node applications, so when it's time to go live, you will need to find a hosting service for the frontend. - -That's why we've packaged the frontend app in a Docker container, which can be deployed to a hosting provider with Docker support like Amazon Web Services or Google Cloud Platform. For a fast, easier alternative, check out [Now](https://zeit.co/now). +If you're hosting WordPress on a traditional WordPress hosting provider like BlueHost, DreamHost, or SiteGround, when it's time to go live, you will likely need to find a hosting service for the frontend. That's why we've packaged the frontend app in a Docker container, which can be deployed to a hosting provider with Docker support like Amazon Web Services or Google Cloud Platform or for a fast, easier alternative check out [Now](https://zeit.co/now). To run the Docker container locally: @@ -81,6 +79,13 @@ To run the Docker container locally: > yarn run deploy ``` +Or, you can deploy both the WordPress application and frontend to a cloud platform and leverage that cloud's SQL and media storage services. There's a large number of possible options you could use, including: + +- App Engine PaaS on Google Cloud Platform ([setup guide](https://computerlab.io/2018/12/20/deploying-headless-wordpress-on-gcp/) +- Elastic Beanstalk PaaS on AWS +- Managed Kubernetes services like GKE / AKS +- PaaSes / VMs provided by any cloud + ## Troubleshooting Common Errors **Breaking Change Alert - Docker** From e80af5f46459717ffc54814f7ed77bc0496dc3bb Mon Sep 17 00:00:00 2001 From: Patrick Steadman Date: Thu, 20 Dec 2018 12:10:29 -0500 Subject: [PATCH 2/2] fix typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9a8bb941..0b4496be 100644 --- a/README.md +++ b/README.md @@ -81,7 +81,7 @@ To run the Docker container locally: Or, you can deploy both the WordPress application and frontend to a cloud platform and leverage that cloud's SQL and media storage services. There's a large number of possible options you could use, including: -- App Engine PaaS on Google Cloud Platform ([setup guide](https://computerlab.io/2018/12/20/deploying-headless-wordpress-on-gcp/) +- App Engine PaaS on Google Cloud Platform ([setup guide](https://computerlab.io/2018/12/20/deploying-headless-wordpress-on-gcp/)) - Elastic Beanstalk PaaS on AWS - Managed Kubernetes services like GKE / AKS - PaaSes / VMs provided by any cloud