<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Self-Hosting on jonson.io</title>
    <link>https://jonson.io/tags/self-hosting/</link>
    <description>Recent content in Self-Hosting on jonson.io</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 27 Dec 2025 09:48:35 -0500</lastBuildDate>
    <atom:link href="https://jonson.io/tags/self-hosting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Podman Quadlets: A better docker vpn?</title>
      <link>https://jonson.io/posts/podman-quadlets-better-docker-vpn/</link>
      <pubDate>Sat, 27 Dec 2025 09:48:35 -0500</pubDate>
      <guid>https://jonson.io/posts/podman-quadlets-better-docker-vpn/</guid>
      <description>&lt;p&gt;If you need to run a docker container (or multiple) and restrict it to a specific vpn, &lt;a href=&#34;https://github.com/qdm12/gluetun&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;gluetun&lt;/a&gt; seems to be the de-facto way to do it.  And it works great, for that specific container.  But it gets a bit messy when you want to have other containers route their traffic through it, especially if you&amp;rsquo;re running this as a lightweight container in &lt;a href=&#34;https://www.proxmox.com/en/products/proxmox-virtual-environment&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;proxmox&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;I recently stumbled upon &lt;a href=&#34;https://docs.podman.io/en/latest/markdown/podman-pod.1.html&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;podman pods&lt;/a&gt; and &lt;a href=&#34;https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;quadlets&lt;/a&gt;, and it felt like these might be a better way to do it?  For my use case, I&amp;rsquo;m using an unprivileged LXC container running in proxmox, but this should apply anywhere.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Deploying an app using dokku</title>
      <link>https://jonson.io/posts/deploying-app-dokku/</link>
      <pubDate>Mon, 06 Jan 2025 03:10:42 +0000</pubDate>
      <guid>https://jonson.io/posts/deploying-app-dokku/</guid>
      <description>&lt;h2 id=&#34;background&#34;&gt;&#xA;  Background&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#background&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;I recently set up &lt;a href=&#34;https://dokku.com/&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;dokku&lt;/a&gt; to host a handful of self-hosted and personal apps.  Fast-forward a few months and I can&amp;rsquo;t remember how to deploy a new app with my setup &amp;#x1f602;&lt;/p&gt;&#xA;&lt;p&gt;For my future self, I&amp;rsquo;m going to document here how to deploy &lt;a href=&#34;https://mealie.io/&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;mealie&lt;/a&gt;, which at the time of writing suggests the following docker compose file.  This can be adapted for anything that can be deployed with a single Dockerfile.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
