<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Life Meets Code</title>
    <link>https://lifemeetscode.com/</link>
    <description>Recent content on Life Meets Code</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 30 Sep 2017 16:22:30 -0600</lastBuildDate><atom:link href="https://lifemeetscode.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>About</title>
      <link>https://lifemeetscode.com/about/</link>
      <pubDate>Tue, 21 Feb 2023 19:33:28 -0600</pubDate>
      
      <guid>https://lifemeetscode.com/about/</guid>
      <description>Greetings, I&amp;rsquo;m Adam Kammeyer! I&amp;rsquo;m a father, recreational developer, manager, avid comic book reader, and wishful cyclist. I&amp;rsquo;ve been working in I.T. in some fashion for almost 20 years. My current obsessions are my blended family, self-hosting services, and home automation. All the computers in my home run Linux. I may have a Raspberry Pi addiction.
My hope is to use this site to share my experiences and my knowledge with the world.</description>
    </item>
    
    <item>
      <title>Deploying Life Meets Code Web Server</title>
      <link>https://lifemeetscode.com/posts/deploying-life-meets-code-web-server/</link>
      <pubDate>Sat, 30 Sep 2017 16:22:30 -0600</pubDate>
      
      <guid>https://lifemeetscode.com/posts/deploying-life-meets-code-web-server/</guid>
      <description>The first part of this series dealt with setting up and securing the operating system for our server. Now we will take a look at getting Apache up-and-running with TLS.
Note: During my initial setup, I used Vultr&amp;rsquo;s Firewall to only allow traffic from my IP address. That way I could work without the fear of information disclosure.
Apache Apache itself is simple to install. We&amp;rsquo;ll include mod_ssl to allow support for https.</description>
    </item>
    
    <item>
      <title>Deploying Life Meets Code the Server</title>
      <link>https://lifemeetscode.com/posts/deploying-life-meets-code-the-server/</link>
      <pubDate>Sat, 26 Aug 2017 16:07:04 -0600</pubDate>
      
      <guid>https://lifemeetscode.com/posts/deploying-life-meets-code-the-server/</guid>
      <description>I want to keep a record of how I configured the server for this site and decided to share that info to help others and (hopefully) improve my setup. I&amp;rsquo;ve used DigitalOcean in the past, but decided to try out Vultr to host my site. I use CentOS for my servers so I used Vultr&amp;rsquo;s CentOS 7 x64 image as the base. From my Vultr account dashboard, I chose the $2.</description>
    </item>
    
    <item>
      <title>Fedora 26 Upgrade</title>
      <link>https://lifemeetscode.com/posts/fedora-26-upgrade/</link>
      <pubDate>Mon, 24 Jul 2017 15:59:54 -0600</pubDate>
      
      <guid>https://lifemeetscode.com/posts/fedora-26-upgrade/</guid>
      <description>Fedora 26 was released on July 11, 2017. Being a Fedora user, I wanted to upgrade immediately. :) Since I didn&amp;rsquo;t have any issues during the 24 to 25 upgrade, I had confidence this would be as sommoth. I had just reinstalled Fedora 25 a week before 26 was launched so my system was relatively clean. I followed the blog post on upgrading through the Software Center and wanted to share my experience.</description>
    </item>
    
    <item>
      <title>Raspberry Pi With Gps</title>
      <link>https://lifemeetscode.com/posts/raspberry-pi-with-gps/</link>
      <pubDate>Mon, 22 May 2017 16:40:31 -0600</pubDate>
      
      <guid>https://lifemeetscode.com/posts/raspberry-pi-with-gps/</guid>
      <description>After receiving a Raspberry Pi Zero for Christmas, I struggled to find a project to use it with. I started looking around and came across the MagPi issues that listed project ideas for the Zero and Zero W (a Zero with built-in Wi-FI and Bluetooth). In Issue 40, there was a tutorial on creating a GPS Logger with a Zero. I was already on a path to take more control of my own data and tracking bike routes was one thing that was escaping me.</description>
    </item>
    
    <item>
      <title>Taking Notes With Nextcloud Qownnotes and Notebooks</title>
      <link>https://lifemeetscode.com/posts/taking-notes-with-nextcloud-qownnotes-and-notebooks/</link>
      <pubDate>Wed, 17 May 2017 15:49:10 -0600</pubDate>
      
      <guid>https://lifemeetscode.com/posts/taking-notes-with-nextcloud-qownnotes-and-notebooks/</guid>
      <description>I&amp;rsquo;ve seen a lot of people on Twitter recently asking for advice on taking notes. Mostly as alternative to Evernote. I&amp;rsquo;ve shared my setup when I can, but 140 characters only goes so far, so I thought I&amp;rsquo;d write up something more in-depth. Personally, I like the ability to jot down something on-the-go and then do something with it later. That means I need a way to sync file from my phone to my PC.</description>
    </item>
    
    <item>
      <title>Timing Linux Bash Commands</title>
      <link>https://lifemeetscode.com/posts/timing-linux-bash-commands/</link>
      <pubDate>Sun, 26 Mar 2017 15:46:03 -0600</pubDate>
      
      <guid>https://lifemeetscode.com/posts/timing-linux-bash-commands/</guid>
      <description>While updating some Vagrant config files, I was curious how long it was taking for a box to build from scratch. I tried dumping out timestamps directly in the Vagrantfile, but ultimately decided to look for a Bash-specific method that would be more universal and let me time some other Linux commands. Here&amp;rsquo;s what I came up with.
Open your .bashrc in your favorite text editor.
$ vim ~/.bashrc Add this function to the end of the file</description>
    </item>
    
    <item>
      <title>Detecting Wi-Fi Channels in Linux</title>
      <link>https://lifemeetscode.com/posts/detecting-wi-fi-channels-in-linux/</link>
      <pubDate>Thu, 09 Mar 2017 08:34:28 -0600</pubDate>
      
      <guid>https://lifemeetscode.com/posts/detecting-wi-fi-channels-in-linux/</guid>
      <description>Recently I&amp;rsquo;ve been diagnosing some WI-FI connection issues at home and needed a way to find what channels were being used. In the past, I&amp;rsquo;ve used an app on an old Android phone I had lying around, but decided I needed a more practical way. So I set off to DuckDuckGo for an answer.
It didn&amp;rsquo;t take long to find a couple of nice command-line solutions.
First, find the name of your wireless adapter using</description>
    </item>
    
  </channel>
</rss>
