https://kaveland.no/tags/caddy/Recent content in Caddy on Robin's blogHugo -- 0.145.0en-usWed, 14 May 2025 18:00:00 +0000https://kaveland.no/posts/2025-05-14-fire-and-forget-linux-p3/Wed, 14 May 2025 18:00:00 +0000https://kaveland.no/posts/2025-05-14-fire-and-forget-linux-p3/<p>This post is part of the series on no-ops linux deployment. The <a href="https://kaveland.no/posts/2025-05-13-fire-and-forget-linux-p1">first post</a> covered local development of linux server configuration and essential configuration. The <a href="https://kaveland.no/posts/2025-05-14-fire-and-forget-linux-p2">previous installment</a> covers a janky podman installation and configures a reverse proxy to send traffic to a simple container deployment. This is the <a href="https://kaveland.no/posts/2025-05-14-fire-and-forget-linux-p3">final post</a>. It covers a more challenging deployment with jobs and rolling restarts, and discusses the strengths and weaknesses of this approach to hosting.</p> <p>After the previous post, we know how to deploy a container that requires absolutely no configuration and restarts almost instantly. Most of the applications I work on in my daytime job aren&rsquo;t like that. Let&rsquo;s take a look at a more complex example.</p>https://kaveland.no/posts/2025-05-14-fire-and-forget-linux-p2/Wed, 14 May 2025 00:00:00 +0000https://kaveland.no/posts/2025-05-14-fire-and-forget-linux-p2/<p>This post is part of the series on no-ops linux deployment. The <a href="https://kaveland.no/posts/2025-05-13-fire-and-forget-linux-p1">previous post</a> covered local development of linux server configuration and essential configuration. <a href="https://kaveland.no/posts/2025-05-14-fire-and-forget-linux-p2">This installment</a> covers a janky podman installation and configures a reverse proxy to send traffic to a simple container deployment. The <a href="https://kaveland.no/posts/2025-05-14-fire-and-forget-linux-p3">final post</a> covers a more challenging deployment with jobs and rolling restarts, and discusses the strengths and weaknesses of this approach to hosting.</p> <p>At the completion of the previous post, we had automatic installation of a functional Ubuntu server with the bare essentials installed. We did this by writing a <code>base-install</code> ansible role. There&rsquo;s still a missing ingredient before we can start deploying containers, though!</p>https://kaveland.no/posts/2025-05-13-fire-and-forget-linux-p1/Tue, 13 May 2025 00:00:00 +0000https://kaveland.no/posts/2025-05-13-fire-and-forget-linux-p1/<p>In <a href="https://kaveland.no/posts/2025-04-14-running-containers-on-the-cheap">Running containers on no-ops linux in 2025</a> I wrote about moving my hobby projects to a European cloud provider. I did an initial, manual setup in <a href="https://www.hetzner.com/">Hetzner</a>, which I&rsquo;ve now automated. This weekend, I tested the setup. It takes me a few minutes now to get everything moved to a new host, and most of that has to do with DNS. I&rsquo;ve got a reproducible setup, I can quickly provision up a machine locally or in any cloud that has Ubuntu 24.04. Reproducible infrastructure is ✨liberating✨</p>