| In the middle of building a self-hosting setup at home so I went ahead and installed this to give it a trial run. I generally like the interface and think it is a nice take on making self-hosting easier, but I have some pure stream of conscious criticism: 1. There sure are a lot of crypto apps. I'm not vehemently anti-crypto, but it is missing some "obvious" applications and full of those, so I'm curious what the play was there. They're all spread all over the place isntead of in a single category too. There are non-crypto finance apps that are self-hosted (Actual, BudgE, etc.), please don't mix them. 2. Plex and/or jellyfin stand out as huge misses right out of the gate. 3. I am surprised that it doesn't use nginx proxy manager with preset configs to make this all available from a single domain. Needs letsencrypt + a DDNS provider too while you're at it. 4. Why no blog/cms? 5. Can I give it the docker-compose config for an application not on the app store somewhere in GUI? 6. Wait, why is this accessible from Tor? And I can't turn it off? Nope nope nope. |
1. Re crypto apps, I figured some additional context may help. Before our today's release, Umbrel was a self-hosting OS primarily geared towards Bitcoin node users. Today, we migrated the Bitcoin node to the Umbrel App Store and took the last step in our transition to becoming an app-agnostic general purpose OS. So expect to see a lot more non-Bitcoin apps hereon!
2. Yes, agree. We'll have Plex and Jellyfin live in the app store soon.
3. The main issue we found with using a single domain on the local network is that many Android phones and PCS have flaky mDNS support, in which case name resolution for "*.local" would simply fail. This is why we decided to use ports. Perhaps we can look into using ports on the local network and domain on a VPS.
4. Good suggestion! Feel free to share your recommendations.
5. That's not possible using the UI, but you can create your own custom docker-compose app by following our app framework documentation: https://github.com/getumbrel/umbrel-apps/blob/master/README....
6. Until now, a common use case of our users has been remote connection between Umbrel and their Bitcoin wallets over Tor. This is why remote access was baked directly into Umbrel and turned-on by default.
However, as we've now evolved from the Bitcoin space, we'll prioritize offering the ability to disable remote Tor access functionality in the next update, and make it opt-in instead of opt-out.