<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>stp5.net</title><link>https://stp5.net/</link><description>Recent content on stp5.net</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 09 Mar 2017 10:05:23 -0800</lastBuildDate><atom:link href="https://stp5.net/index.xml" rel="self" type="application/rss+xml"/><item><title>ChatOps and Cog</title><link>https://stp5.net/blog/post/chatops-and-cog/</link><pubDate>Thu, 09 Mar 2017 10:05:23 -0800</pubDate><guid>https://stp5.net/blog/post/chatops-and-cog/</guid><description>ChatOps: A Brief History If you&amp;rsquo;ve been in the DevOps space over the past few years, you&amp;rsquo;ve probably heard the term &amp;ldquo;ChatOps&amp;rdquo; thrown around. If not, there&amp;rsquo;s a simple definition:
ChatOps: Performing Operations tasks in group chat.
A good example of this would be kicking off a deployment to production by typing a command in a chat room.
There are plenty of videos and slidedecks of the power of this approach, but I&amp;rsquo;ll just include GitHub&amp;rsquo;s here:</description></item><item><title>Secrets in AWS</title><link>https://stp5.net/blog/post/secrets-in-aws/</link><pubDate>Mon, 06 Mar 2017 10:59:35 -0800</pubDate><guid>https://stp5.net/blog/post/secrets-in-aws/</guid><description>Managing secrets in the cloud Moving hosted services to cloud-based archictectures has introduced a lot of different pain points, some new, some pre-existing that become more of an issue. One such issue is secrets1.
There have been a number of different discussions and solutions for this problem, including:
Hacker News: Ask HN: In a microservice architecture, how do you handle managing secrets? Docker GitHub: Secrets: write-up best practices, do&amp;rsquo;s and don&amp;rsquo;ts, roadmap The main question here is: &amp;ldquo;How do you expose secrets to only those services that require them, without exposing them to those that don&amp;rsquo;t, and at the same time make their lifecycle (rotating/replacing/expiring) easy to maintain?</description></item><item><title>Serverless Blog</title><link>https://stp5.net/blog/post/serverless-blog/</link><pubDate>Fri, 03 Mar 2017 14:19:28 -0800</pubDate><guid>https://stp5.net/blog/post/serverless-blog/</guid><description>Hello from CloudFront As of today, this blog is now being served by Amazon S3, and cached globally by CloudFront. You can say it&amp;rsquo;s &amp;ldquo;serverless&amp;rdquo;, even if the term isn&amp;rsquo;t quite true (after all, it&amp;rsquo;s always running on someone&amp;rsquo;s server). The transition wasn&amp;rsquo;t too easy, but it was my first crack at hosting a site purely in S3, and it was a chance to learn to use CloudFront and Travis CI.</description></item><item><title>From Debian to CoreOS</title><link>https://stp5.net/blog/post/from-debian-to-coreos/</link><pubDate>Fri, 23 Sep 2016 12:05:10 -0700</pubDate><guid>https://stp5.net/blog/post/from-debian-to-coreos/</guid><description>Moving to CoreOS Just a quick entry here. Historically this site has been running on a Digital Ocean Debian droplet. I liked having a remote Linux host that I could run random things on, including this blog.
However, recently I&amp;rsquo;ve only been using it to run things within Docker containers. Since CoreOS was designed for exactly this purpose, I decided to try setting up a single-host cluster as a DO droplet.</description></item><item><title>Yubikey, Keybase and SSH</title><link>https://stp5.net/blog/post/yubikey-keybase-and-ssh/</link><pubDate>Thu, 15 Sep 2016 16:09:36 -0700</pubDate><guid>https://stp5.net/blog/post/yubikey-keybase-and-ssh/</guid><description>History About a year ago, I purchased a Yubikey NEO, a hardware-based two-factor authentication keyfob. I&amp;rsquo;d had an earlier version that could generate tokens upon being pressed, but the NEO included a few things I wanted to test out, including the ability to store gpg keys on it. I was also curious to see how hard it&amp;rsquo;d be to use the Yubikey with SSH connections. I went through the entire setup a year ago, got frustrated with using GPGTools on OS X and the keychain, and then promptly forgot about it for a year until my key expired and I&amp;rsquo;d forgotten the passphrase I&amp;rsquo;d use to encrypt it.</description></item><item><title>Docker lifecycle with Caddy</title><link>https://stp5.net/blog/post/docker-lifecycle-with-caddy/</link><pubDate>Fri, 06 May 2016 10:15:18 -0700</pubDate><guid>https://stp5.net/blog/post/docker-lifecycle-with-caddy/</guid><description>Caddy was recently updated to 0.8.31. My website&amp;rsquo;s Docker image was built with the previous version, so I had to update the corresponding Dockerfile and rebuild it on the Docker Hub2.
To update the container running on my DigitalOcean droplet, I just ran the following:
docker pull steeef/stp5net docker stop stp5net docker rm stp5net docker run -d --restart unless-stopped &amp;lt;environment-specific-options-here&amp;gt; --name stp5net steeef/stp5net Notice I&amp;rsquo;m using the --restart unless-stopped restart policy3 for the run command.</description></item><item><title>raspberry pi projects</title><link>https://stp5.net/blog/post/raspberry-pi-projects/</link><pubDate>Thu, 07 Apr 2016 11:07:11 -0700</pubDate><guid>https://stp5.net/blog/post/raspberry-pi-projects/</guid><description>Interesting Raspberry Pi Projects I have a few Raspberry Pi Model B&amp;rsquo;s laying around, and I&amp;rsquo;ve been meaning to try out some things with them. I also bought the recently-released Raspberry Pi 3 that I wanted to find a use for.
Pi-hole Pi-hole, put simply, is an ad-blocking, anti-tracking DNS server that you can use in your home network. It was super-easy to set up, and even has a pretty web interface for viewing stats:</description></item><item><title>Caddy and Let's Encrypt</title><link>https://stp5.net/blog/post/caddy-and-lets-encrypt/</link><pubDate>Fri, 01 Apr 2016 10:15:34 -0700</pubDate><guid>https://stp5.net/blog/post/caddy-and-lets-encrypt/</guid><description>Note: this is a follow-up to my earlier post on setting up Caddy with Docker, which is here.
I&amp;rsquo;ve just enabled Caddy&amp;rsquo;s Automatic HTTPS function, which leverages Let&amp;rsquo;s Encrypt to generate a key and get a signed certificate as soon as the server starts up. It&amp;rsquo;s free and simple. Awesome!
I was able to figure this out by reading the official documetation on Automatic HTTPS1 and Abiola Ibrahim&amp;rsquo;s example Dockerfile for Caddy, which included a nice section on how to persist the .</description></item><item><title>Using Docker in OS X with DLite</title><link>https://stp5.net/blog/post/using-docker-in-os-x-with-dlite/</link><pubDate>Thu, 31 Mar 2016 10:47:33 -0700</pubDate><guid>https://stp5.net/blog/post/using-docker-in-os-x-with-dlite/</guid><description>The Past If you&amp;rsquo;ve ever used Docker in OS X, you&amp;rsquo;re probably familiar with the pain of being forced to run a Linux VM to test Docker containers. I&amp;rsquo;ve personally spent hours troubleshooting problems while using boot2docker and its successor, docker-machine. Historically, relying on VirtualBox for anything in OS X development has never been painless (though I&amp;rsquo;ll admit it&amp;rsquo;s improved over the past few years).
xhyve Luckily, there&amp;rsquo;s a better way.</description></item><item><title>Creating my blog with Docker, Hugo, and Caddy</title><link>https://stp5.net/blog/post/creating-my-blog-with-docker-hugo-and-caddy/</link><pubDate>Wed, 30 Mar 2016 13:28:14 -0700</pubDate><guid>https://stp5.net/blog/post/creating-my-blog-with-docker-hugo-and-caddy/</guid><description>A lonely web server I pay for a small DigitalOcean droplet running Debian. I originally created it just to have a remote server with which to play around with various tools. One of which was to host a static site via nginx running in a Docker container. Nothing&amp;rsquo;s really changed with it since that initial setup, save running the container with systemd-nspawn1.
Let&amp;rsquo;s get blogging Fast forward a few years, and I&amp;rsquo;ve been itching to try out some newer technologies.</description></item><item><title>Stephen Price</title><link>https://stp5.net/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://stp5.net/about/</guid><description>About me I live in Portland, Oregon, USA. I&amp;rsquo;m current a Site Reliability Engineer, formerly a Systems Administrator.
I love tinkering with computers to get them to do what I want. I&amp;rsquo;ve dabbled in various Raspberry Pi projects, using Home Assistant to automate my home (or make it more confusing for my family to turn on lights). In my basement, I run a handful of Debian servers based on small computers I&amp;rsquo;ve collected over the years.</description></item></channel></rss>