- GCP: https://reader.doliver.net (https://tw-reader-erpc3bdnvq-uw.a.run.app)
- Netlify: https://tw-reader.netlify.com/
- Surge: https://tw-reader.surge.sh/
GCP | Dashboard
GCP hosts the back end server and connects to DB at Mongo Atlas
Build and deployment are done from the GCP console:
- Login to dashboard and open a cloud shell
- there is a local branch on that machine called
gcp-deployment. The proper environment variables are in the Dockerfile in this branch. - pull origin/master into that branch
git pull origin master - Build a new image with
npm run gcp-build - Deploy the image with
npm run gcp-deploy - Note: don't push anything back to master from here
Netlify | Dashboard
- serves react app only and connects to the GCP back end
- connected to github repo, does auto build & deploy on commits to master
- env vars are defined in netlify.toml
Surge hosts only the React front end of the app and connects to the back end at GCP. This is an alternative to Netlify with a simple push from command line. For any changes to the React app, run a new build and push it to Surge:
- Make sure the following environment variable is set before building:
export REACT_APP_URL_BASE=https://reader.doliver.net - Run the build from the react-app/ directory:
npm run build - Deploy to Surge from the react-app/ directory:
npm run deploy-surge
Note: If the app is unable to load tweets, view the network traffic to make sure it's hitting the reader.doliver.net server. If it's trying to hit surge.sh then the environment variable was probably not set in #1 before the app was built.