Just over 2 years ago I relaunched and moved to Ghost. At the time, my reasoning was simple:
Just over 2 years ago I relaunched and moved to Ghost. At the time, my reasoning was simple:
Recently posted on my main webpage in the other section, is a PDF of a presentation I gave at the Baltimore Elixir and Erlang Meetup. I covered how I got a simple Elixir project testing on Codeship’s docker platform.
Recently posted on my main webpage in the other section, are PDFs of presentations I gave at the Baltimore Elixir and Erlang Meetup. I’m really enjoying working with Elixir and Ansible (see my previous post on Ansible).
The other day I quit working with one of my Chef repositories for some servers I manage. I quit in rage. I quit because nothing worked how I wanted it to.
Just posted on my main webpage in the other section, a PDF of a presentation I gave during lunch at work.
I believe that it is best to understand the configuration and behavior of the tools I use. I don’t appreciate a ‘black box’ approach to technology. I’ve always wanted to understand how and why things work the way they do.
Just posted on my main webpage in the other section, a PDF of a presentation I gave at lunch one day at work.
There is a common pattern I’ve seen, in guides about Ruby on Rails deployment via Capistrano, to setup a maintenance pages or a maintenance mode. The guides help you configure nginx such that the existence of the maintenance page causes the nginx proxy to return the maintenance page instead of forwarding on to the unicorn/puma/passenger server.
It is easy to create a hugely complex disaster recovery plan with all kinds of redundancy and failover. It is also easy to spend a ton of money doing so. There are cases however, where a daily snapshot, and the ability to boot up that most recent snapshot, is plenty of protection.
Coming up at the end of April, it will have been one year since I relaunched my website and blog. I’m going to take this opportunity to reflect on this past year.