This post is a bit similar to last week’s because it describes a solution I came up with for an issue in writing my automated deployment to Dokku series (link to first post): how to programmatically link to other posts in a series without having to manually write markdown links.
For a while I’ve been looking for a way to schedule posts for this blog, which is being hosted on Github Pages. Because Jekyll is a static site generator and not a full CMS, there isn’t an inbuilt way to do it. I had found a post about using Zapier to merge in feature-branches for every new post to get this working, but when I was looking at it, it didn’t really appeal, in large part because it requires giving full access to your repo to Zapier.
When I started putting together the automated dokku test and deployment series (link to first post), it got to the point where I needed scheduling, because I was writing the posts on vacation all at once, but didn’t want them to go live all at the same time. So I ended up hacking together a quick and dirty fix with a VPS running a cronjob.
I’ve been reading a fair bit of Coraline Ehmke’s writing in the last couple of days after her post about her year at Github went viral. Which lead me to her post on Model View Culture, The Dehumanizing Myth of Meritocracy. I haven’t thought about Utilitarianism in a long time, but I have for that time considered myself one, passively at least. The article has made me reconsider that.
I’ve been thinking long and hard about what I might be celebrating today. A lot has changed since the last 4th of July.
This release implements tracking changes to short URLS with paper_trail.
Previously in the series, I’ve focused on setting up and using Dokku. This post is less Dokku focused, and more on making sure that you keep all the precious data you generate and collect with the apps on it safe.
In the first two posts of the series, I looked at setting up Dokku and setting up automated builds and testing with Codeship, Code Climate, and Hakiri. This one ties those two together and covers the process I’m using for automated deployments with Dokku and Codeship (and the gotchas I hit along the way).
This release implements basic tracking of short URL usage. It tracks the following data:
This release protects the application’s domain from being redirected to by the app to avoid possible infinite loops or inaccessible application routes.
Last time in the Dokku series I went through how I set up Dokku on a VPS. This one is going to be about setting up Codeship, Code Climate and Hakiri (Ruby only, though the principles should be pretty similar for other languages/frameworks) to automate builds and testing. Should be a bit shorter, because there were fewer gotchas in this than in setting up Dokku (not that there were many there!)
