Continuous Deployment of a Static Website
This guide shows you how to use Semaphore to set up continuous deployment for a static website. Before starting, create a new Semaphore project.
Define the pipeline
There are many static site generators, but the essential deployment steps are the same for all:
- Install the tools to generate the site, along with their dependencies;
- Build the website from source files;
- Upload the website files to cloud storage or host.
We'll start by setting up a Semaphore pipeline which maps the first two steps to blocks. If all blocks run successfully on master branch, we'll automatically promote the code to the deployment pipeline.
This configuration also uses caching to store project's dependencies, and pass the website files to the deployment pipeline.
The example is based on a static website built with a Node.js toolchain. Change the dependency installation and site building steps to match your tools.
# .semaphore/semaphore.yml version: v1.0 name: "Deploy website" agent: machine: type: e1-standard-2 os_image: ubuntu1804 blocks: - name: "Install dependencies" task: jobs: - name: npm install commands: - checkout # Reuse dependencies from cache and avoid installing them from scratch: - cache restore node-modules-$(checksum package-lock.json) - npm install - cache store node-modules-$(checksum package-lock.json) node_modules - name: "Build site" task: jobs: - name: Build commands: - checkout - cache restore node-modules-$(checksum package-lock.json) # Replace this with command(s) that build your website: - npm run build:all # The script puts website files in directory `public`, # store it in cache to propagate to deployment: - cache store website-build public promotions: - name: Production deploy pipeline_file: production-deploy.yml auto_promote_on: - result: passed branch: - master
Configure deployment credentials
In this example, we'll deploy our static website to AWS S3. To do that, we need to use valid AWS credentials. A secure way to pass our credentials to Semaphore is by defining a secret.
Create a new secret based on local
~/.aws configuration files:
sem create secret aws-website \ --file ~/.aws/config:/home/semaphore/.aws/config \ --file ~/.aws/credentials:/home/semaphore/.aws/credentials
The above ensures that the files sourced from our local machine will be placed in the home directory of the user which executes our code on Semaphore.
Finally, create a file
.semaphore/production-deploy.yml to execute deployment, and import the secret for authentication to work:
# .semaphore/production-deploy.yml version: v1.0 name: Deploy website agent: machine: type: e1-standard-2 os_image: ubuntu1804 blocks: - name: Deploy task: secrets: - name: aws-website jobs: - name: Copy to S3 commands: - checkout - cache restore website-build - ./scripts/deploy
That’s it. Your website will now be continuously deployed every time there is a valid change on master branch. Deployment won't run on other branches and pull requests. However, Semaphore will report a build failure in case there's an error which prevents the website to be generated, so that you can fix it before merging to master.