Now that we have our backend deployments automated, we are ready to do the same for our frontend React app. Just like the backend CI/CD pipeline, we can use something like Travis CI or CircleCI. But these take a lot of scripts and configuration to set up.
Here’s what the CI/CD pipeline for our React app will look like.
Let’s go over the workflow.
- Our repo will be connected to our CI/CD service.
- Any commits that are pushed to the
masterbranch will be automatically built and deployed under our production url.
- While any other commits that are pushed to a non-master branch, will be built and deployed to a unique development url.
There are a couple of differences between our backend workflow and frontend workflow. When we merge our changes and push to master, they are automatically deployed under our production url. We are not using a manual approval step because our React app is a simple static site. So even if we make any mistakes there’s no chance of a data loss.
The one thing we haven’t done for our React app is set up environments. We want our development branches to connect to our development backend resources. And likewise for our production branch. We’ll need to do this before we can automate our deployments.
So let’s do that next!