Our great sponsors
-
umbrel
A beautiful home server OS for self-hosting with an app store. Buy a pre-built Umbrel Home with umbrelOS, or install on a Raspberry Pi 4, Pi 5, any Ubuntu/Debian system, or a VPS.
-
umbrel-apps
The official app repository of the Umbrel App Store. Submit apps and updates here. Learn how → https://github.com/getumbrel/umbrel-apps#readme
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
> It's a perfectly justifiable decision...
Especially when one of the VC firms that funds your project is also the one behind formulation of the Polyform set of licenses, I'd imagine. At least, it is better than a fully closed-source code, too, that is built atop MIT/BSD/Apache licensed projects (say, the V8 JavaScript engine ;), but never shared.
The only reason I dislike non-OSI approved licenses are, the "users" of such licenses want to have their cake and eat it too: As in, they want to project open source ethos while also denying the advantages/rights otherwise afforded by Open Source, as defined by the OSI.
Imo, source-available licenses are justified only when companies using it are honest about their intentions and forthcoming about the license's limitations.
Nothing specific on Umbrel but generally an off-putting behaviour among firms insistent on source-available licenses even if they're out commoditizing their core advantage themselves! I've followed Umbrel project since I first knew about it in August 2020, and of course, I'd have liked them to be open-source: https://github.com/getumbrel/umbrel/issues/291#issuecomment-...
Thanks for the taking the time to try Umbrel out, great observations!
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.
Re 3: What you really need is Caddy [0] with this dynamic DNS module: https://github.com/mholt/caddy-dynamicdns
Caddy has state-of-the-art certificate automation and TLS support, and with that module, it automatically updates DNS records if users have non-static IPs. It'll also serve certs for localhost domains (use *.localhost IMO).
[0]: https://caddyserver.com (I'm the author, for disclosure)
Re 3: What you really need is Caddy [0] with this dynamic DNS module: https://github.com/mholt/caddy-dynamicdns
Caddy has state-of-the-art certificate automation and TLS support, and with that module, it automatically updates DNS records if users have non-static IPs. It'll also serve certs for localhost domains (use *.localhost IMO).
[0]: https://caddyserver.com (I'm the author, for disclosure)
If you are reading this please take a look at start9. https://start9.com/
The major problem with Umbrel is that even though they package all in one-solutions. If something goes wrong you rely on umbrel for issues (against decentralization). You will rely on their updates for any problems.
start9 built an linux os group up. all services are individually packaged from source.
umbrel packages all dependencies together (via docker container) which could causes issues for maintenace.
// start9 vs umbrel