Longer ago than I’d like to admit, I put together a DIY Peloton bike to participate in Peloton Digital classes. I used it pretty consistently at first, but never formed a habit.
Longer ago than I’d like to admit, I put together a DIY Peloton bike to participate in Peloton Digital classes. I used it pretty consistently at first, but never formed a habit.
In the new project I mentioned in the previous post, I’m focusing on practicing good habits, which my CI setup is a large part of. The other big part is keeping things clean and well written before they are even committed into the repository.
Recently, I started a new side project (maybe more on that soon), and I decided to give GitLab a try. I’ve used it for some client work through my job, but had never really messed with it on my own.
I’ve mentioned a few times how I’ve moved to use Ansible more and more for server provisioning and change management.
October was National Cyber Security Awareness Month. On the company blog I wrote up a 3 post series about building acceptable security when creating custom web and mobile applications.
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.
Back when I migrated from Ghost to Jekyll, one thing I gave up was a really easy to use Markdown editor with a side-by-side preview.
I’m continuing to really enjoy working with Ansible. It meets the needs I have for server configuration, and has a lot of great community resources.
My design skills are wanting. I’m much more focused on backend development. I can cobble together pieces, but I’m far from expert.
I’ve been using Ansible more and more. It is a really great way to manage server configuration. As I’ve transitioned away from Chef, I’ve been working on establishing some patterns that seem to work well when setting up servers for deploying web applications.