Runtipi: Docker-based home server management

This appears to suffer from the same mistake as many of these things do in this space: it focuses on making it really easy to run lots of software, but has a very poor story when it comes to making the data and time you put in safe across upgrades and issues. The only documented page on backing up requires taking the entire system down, and there appears to be no guidance or provision for safely handling software upgrades. This sets people up for the worst kind of self-hosting failure: they get all excited about setting up a bunch of potentially really useful applications, invest time and data into them, then get burned really badly when it all comes crashing down in an upgrade or hardware failure, with improper preparation. This is how people move back to saas and never look back again, it's utterly critical to get right, and completely missing here.

Personal opinion, a home lab is the perfect place to learn how to actually configure things and properly set them up: no docker, no ansible, no salt… take off the training wheels and learn it. Then, learn to write your own playbooks, your own compose files, etc.<p>Additionally, if people think that learning how to configure and deploy stuff is too tedious and&#x2F;or too difficult, write software that has better UI, not more layers of configuration and administration.<p>Final thought, git is better than ansible&#x2F;salt&#x2F;chef&#x2F;puppet, and containers are silly.

&gt; At its core, Tipi is designed to be easy to use and accessible for everyone<p>&gt; This guide will help you install Tipi on your server. Make sure your server is secured and you have followed basic security practices before installing Tipi. (e.g. firewall, ssh keys, root access, etc.)<p>I love to see efforts like this, please keep it up.<p>But expecting users to learn everything necessary to run a secure server is simply not going to achieve the stated goal of being accessible to everyone.<p>We need something like an app that you can install on your laptop from the Windows store, with a quick OAuth flow to handle all networking through a service like Cloudflare Tunnel, and automatic updates and backups of all apps.

I think this is useful for less tech oriented people to get a basic homelab setup.<p>But I personally find it much more straightforward and maintainable to just use Compose). Virtually every service you would want to run has first-class support for Docker&#x2F;Podman and Compose.

These services are cool but I almost always end up doing it myself anyways. Doing it yourself is more fun anyways.<p>Typically I just make my own one click deploys that fit my preferences. Not knowing how your container starts and runs is a recipe for disaster.

Anyone have any experience using this? I&#x27;ve been managing most of my homelab infrastructure with a combination of saltstack and docker compose files and I&#x27;m curious how this would stack up.

Does anyone have any recommendations on top of this? I personally run portainer and would like more features like grouping containers post creation and container start order. I also have an issue where my VPN container if updated breaks all containers that depended on it. Portainer handles a lot, but I need the little bit more so I have to look at the panel less. I&#x27;m not sure if this would work for me since I build a lot of custom containers and this looks more like it&#x27;s better for purpose built containers.

I find terraform + acme provider + docker provider (w&#x2F; ssh uri) to be the best combo.<p>All my images live on a private GitLab registry, and terraform provisions them.<p>Keeping my infra up-to-date is as simple as &quot;terraform plan -out infra.plan &amp;&amp; terraform apply infra.plan&quot; (yes, I know I shouldn&#x27;t blindly accept, but it&#x27;s my home lab and I&#x27;ll accept if I want to).<p>Note: SSH access is only allowed from my IP address, and I have a one-liner that updates the allowed IP address in my infra&#x27;s L3 firewall.

This looks great and I want something like this to run Vaultwarden, some 2FA manager, a media manager, Syncthing, Next cloud and so on.<p>However I&#x27;m very worried about vulnerabilities in one of the applications getting my entire machine pwned and thus leaking my Vaultwarden data. It feels like this is just one CVE and Docker privilege escape away.<p>What do others think about this? Am I being overly paranoid?

for me it would be a lot of underlying complexity for &quot;just&quot; exposing docker-compose containers to the internet.<p>I don&#x27;t really understand the target audience here. If you need to manage dns, server hardening, backups, upgrades, internet exposing and evaluating the risks behind that, you should be able to do the rest yourself too. And it is single server only

Is this dockerized alternative to <a href="https:&#x2F;&#x2F;yunohost.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;yunohost.org&#x2F;</a> ?

I&#x27;ve been testing Coolify [1] for this, so far the experience has been smooth as a self-hostable Vercel&#x2F;Netlify&#x2F;PaaS replacement.<p>Now onto finding&#x2F;learning host management tools (Ansible, NixOS, Terraform and the like).<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;coollabsio&#x2F;coolify">https:&#x2F;&#x2F;github.com&#x2F;coollabsio&#x2F;coolify</a>

The top section of the site matches very closely another project posted on HN a couple weeks ago - no negative opinion from me, because I also thought it was incredible design and borrowed a ton of it for one of my sites.

How does this differ from Caprover?