But that still does mean it needs to be deployed.
You could deploy just on s3 but for me I already have my own server. So I just deploy it to there.
Regardless, the goal is to deploy to
phrye.com with just a single
git push to the
master branch. Deploying to a test site on
other branches would let me test style and other sorts of changes.
This is accomplished with Gitlab and some tools it provides.
The first part of gitlab that comes into play is Gitlab CI.
This is configured with a
.gitlab-ci.yml at the base of the repo:
This provides for a three stage pipeline when I push to
other branches it doesn’t do the
deploy step (the
only: master bit
build step uses Gitlab Pages to deploy the site to
a site hosted on the gitlab server. So
is an internal site that has a test version of my site. This is
done by running
hugo to generate the stie. This will result in a
output which contains the site. Rename
public and the
pages step will hoover all that up and deploy
it on that internal site.
One little hang up here is that the main deployment is at the root
of the site but the pages site is not. The
--baseURL flag of
hugo will help fix that.
I’ll get into the ci scripts tomorrow.