# A TUI to get into self-hosting — retained record

> Retained reddit record from reddit:homelab.

Canonical: https://highsignal.app/data/records/72c6bfe1c66a65c7

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:homelab)  published 2026-10-30 19:29 ingested 2026-10-31 02:39

[original source ↗](https://www.reddit.com/r/homelab/comments/1xjowy8/a_tui_to_get_into_selfhosting/)

## retained text



```
Last year I built Docker Compose Maker in October 2025. It was a super simple website to help you get a fully working docker compose to get started homelabbing.

Now, one year later I am presenting to you: [self-host.fyi](http://self-host.fyi/), the evolution of DCM.

Self-host is a complete re-write and addition to DCM, it is a simple binary that works for linux, mac, wsl2 & agent skill that aims to get people into self-hosting.  
You pick which services you want through a TUI catalog, and it handles not just deploying every containers but also the setup of accounts, API keys & linking apps together.  
It's just Docker compose underneath. All your config files and your docker setup is inspectable docker compose files. Think of it like a helper for docker compose for new users, some kind of TUI to manage containers, it's like Dokploy, Portainer or CasaOS but directly inside of your terminal.

The most important change is that it will link apps together. It is able to setup Sonarr for you and set Qbittorrent as the download client automatically, by creating an admin account in Qbittorrent and putting its API key into Sonarr directly. The passwords are automatically generated by default and can be manually defined.

You can have a fully running self-hosted setup going with one command, it comes with a fully-configured dashboard to access all your services from if you want to.

For example: I had never tried Mealie but in \~20 seconds of using the TUI it was able to set it up with a random password and connect it to my dashboard. I tried Mealie and figured I won't find the time to log it, it's not for me. With shift + A I selected it and removed it. That's it, less than 5 minutes. 

If you've already got your dream homelab running and perfectly tuned, this isn't for you. It is more geared towards people who are looking into getting into self-hosting or who'd want to try out an app in an easy way.  
Right now we support 93 self-hosted apps and hopefully that covers most people's use cases.  
I've spent extra time to make sure that the SDK the tool uses is super easy to work with so that anyone who knows how to program in Go can suggest additions, there's also a feature to add unsupported apps without coding. 

Anyway, curious what you all think!

website : [self-host.fyi](http://self-host.fyi/)  
repo : [github.com/ajnart/self-host](http://github.com/ajnart/self-host)  
small presentation video: [https://self-host.fyi/#reel](https://self-host.fyi/#reel)

I want to make it clear, **I am not suggesting that an advanced user uses this CLI.** If you have a fully working setup your are proud of you do not need this tool. Think of it like simpler TUI version of Portainer, you can use it to quickly add and try out an app and it'll give you a fully setup version of that app. Or a way to let one of your friend try self-hosting an app you're telling them about, without needing to explain to them how they communicate together. They can simply try using Immich on their machine.  
Then they can decide for themselves if it's worth it to go down the rabbit hole of self-hosting and spend their following weekends refactoring and adding a new container to their stack and debugging until 2am.   
Use it to peak the interest in that friend and invite them to try self-hosting, it will allow them to easily setup \*arr + jellyfin & seerr in 5 minutes, then they might try sailing the seas instead of spending a monthly fortune on rented media they don't own to companies who'd betray them in an instant.

With the recent Sony Playstation bullshit I want to get more and more people to into self-hosting to actually own their data and I feel that a simpler way to get a fully working setup would fit into the space, as an upgrade to DCM. 

AI disclaimer :   
Designed the SDK by hand and identified all the features it would need and built it. Then I worked on support for the "main" \*Arr apps + seerr / jellyfin. Once it was done I decided to extend the catalog to support apps beyond the apps I use. I used agents to research and setup some of the 90+ apps it supports and parallelize the work, both on Linux, Mac, WSL2, ARM & x86, then I had to verify that they all worked and got set-up properly. It would've taken me months of work to make every app support "by hand", especially because most tools don't really have an API. Self-host supports tools that don't have an API, it just mimics the requests used to create accounts and other actions inside of the app for you with your desired credentials, kind of like a playwright script but much faster.

The SDK's code is easy to read and to work with, so it should be pretty straight forward to add new entries to the catalog if you know basic Go. LLMs also helped me create installation scripts for homebrew, debian, arch / omarchy, ... as well as test them in VMs & generate the illustrations & the showreel video. Post fully written by me ofc
```



document fetched 2026-10-31 00:38 · canonical https://reddit.com/r/homelab/comments/1xjowy8/a_tui_to_get_into_selfhosting
