A Cloud Native j.eremy: Content

Following up from this post. As noted, I use Jekyll for content management. The documentation for Jekyll is quite nice and you can see how to create and write posts here.

My general format is quite simple. As an example, this post up until this point looks like this:

1
2
3
4
5
6
7
8
9
10
11

---
title: "A Cloud Native j.eremy: Content"
date: 2020-12-05 12:00:00+0100
---

Following up from [this post][1]. As noted, I use [Jekyll][2] for content
management. The documentation for Jekyll is quite nice and you can see how to
create and write posts [here][3].

My general format is quite simple. As an example, this post up until this point
looks like this:

I have a quick and dirty Makefile that allows me to perform the most common operations:

• make serve turns on Jekylls local preview website so I can preview my changes.
• make build generates the HTML static site files.
• make push uses s3_website to upload the site to S3.
• make all runs both build and push

1
2
3
4
5
6
7
8
9
10

all: build push

serve:
	jekyll serve --future

build:
	jekyll build

push:
	s3_website push

You could just as well use the AWS CLI to upload, or any of a billion other tools that do the job.

My last task is to push my changes to Github, so I add the new post with git add and then commit and push. My ultimate goal is to not need to run jekyll locally: I’ll push to Github, then have a system such as CodeFresh automatically runs make all and publishes the changes for me. We’ll get to that later.