<?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 Mike Jeffs</title>
    <link>https://mikejeffs.dev/blog/self-hosting/</link>
    <description>Recent content in Self-Hosting on Mike Jeffs</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <copyright>Copyright © 2024, Michael Jeffs.</copyright>
    <lastBuildDate>Sat, 31 May 2025 22:33:02 +0100</lastBuildDate>
    <atom:link href="https://mikejeffs.dev/blog/self-hosting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Experimenting With Coolify</title>
      <link>https://mikejeffs.dev/experimenting-with-coolify/</link>
      <pubDate>Sat, 31 May 2025 22:33:02 +0100</pubDate>
      <guid>https://mikejeffs.dev/experimenting-with-coolify/</guid>
      <description>&lt;p&gt;This post serves as a quick introduction to Coolify, and my thoughts about it after playing around with it over the weekend.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-is-coolify&#34;&gt;What is Coolify?&lt;/h2&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://coolify.io/&#34;&gt;Coolify&lt;/a&gt; is a platform as a service (PaaS), like Heroku or Vercel, which allows you to easily deploy your applications, databases and other services to the web. The USP of Coolify in comparison to other PaaS providers is that you self-host it on your server. It is fully agnostic with no lock-in, so you can run Coolify anywhere really, from AWS to your Raspberry Pi.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
