Runtipi: Homeserver management made easy
Runtipi: Homeserver management made easy
It has an 'App store' that's been growing a lot lately. Writing new docker-compose.yaml files is easy (see: https://www.runtipi.io/docs/contributing/adding-a-new-app ), and exposing them behind NAT, e.g. from home it's easy too (see: https://www.runtipi.io/docs/guides/expose-apps-with-cloudflare-tunnels )... But my favorite perk is the folder structure (see: https://www.runtipi.io/docs/reference/folder-structure ), and the fact that 'media' is shared between apps.
You're viewing a single thread.
Let me preface this with that I am an experienced CLI user and with Docker, so this really is not in my interest generally, but getting older and dealing with a variety of other personal issues, having a nice dashboard to deploy things sometimes is just really nice ya know? So I figured I would put on my dusty beginner's hat to get this a run.
For the beginner, it's a nice system to get started and get your feet wet with a no-nonsense app install experience. I tested this in a VM on my desktop and installed Sonarr and Sabnzbd which if you use Docker with these, you know the proper volume mapping is key. They take the hassle out of doing this for the end user. With that said though - file permissions are a bit off and both Sonarr and Sabnzbd needed the proper permissions set for the folders. Not a deal breaker for someone accustomed to the CLI, but for a new self hoster, this can be a bit frustrating.
Their app store is pretty impressive and I guess growing, the install on the server was painless to get running. It's something to keep an eye on, it's in good company with the other ones like Umbel and CasaOS, each has their own qualities.
For those wanting more fine grained control over the apps and installs, Tipi is a bit more opinionated to the port numbers and paths used and you can't easily modify those (at least from what I could tell). In the long run, this is a non issue for the most part if you are starting on a freshly installed server and don't want to handle the challenges of proper path mapping, reverse proxying and so forth. (They include Traefik in the install). Not having to worry if port 3000 is already taken or 8080 is, you can trust that it will handle it and it does!
Thanks for the detailed review! As another user, I agree overall with your experience. Just for the sake of explain how the applications are configured, let me add this. Port numbers are defined in, for example, https://github.com/meienberger/runtipi-appstore/blob/master/apps/sabnzbd/config.json ...Meanwhile, file permissions should be set as PID/GID 1000, according to https://github.com/meienberger/runtipi-appstore/blob/master/apps/sabnzbd/docker-compose.yml
PID/GID 1000
Can I pick your brain on this? I have my folders set to 1000:1000 , Radarr can import the movies folder but Sonarr complains about the tv folder not being writeable by user abc.
The tv folder looks to have the same permissions to me though? Any idea what could be up with that?
To be clear, you have a (user:group) 1000:1000 on both containers? What about having the same mapping of Uid and Gid on the host? I assume the host is a desktop distro, and they usually have it already. You would require the three, so that permissions are "coherent" between each system
Yeah the user:group mapping was correct. I did work it out though. It was the storage volume being full, it presented as not being writeable! My mergerfs config wasn't quite right. As soon as I set it to most free space it was working again.
It's just funny that I didn't get the same error in Radar.