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)
Thanks for an awesome product Matt!!
1. Makes sense, looking forward to progress there.
2. Excellent. I’d consider one of the Wireguard VPN servers be prioritized as well.
3. I wouldn’t use mDNS for it, I would either require and integrate the PiHole configuration or come with a DNS server as well (leaning towards PiHole here). I’d suggest long-term planning on integrating DNS/DDNS and LetsEncrypt. I use a combo of a DDNS container for CloudFlare and a wildcard DNS generated by nginx proxy manager.
4. I’d go for one “simple” CMS, like Ghost, and one fully featured, like WordPress.
5. Will check it out.
6. Appreciate it being an option, I’ve signed up for the mailing list to get a notification when it is available so I can make another run at it.
Great work and I appreciate the engagement.
It would be nice to have first class support for deploying stuff this way - not just for testing. I would like to deploy custom containers / compositions on my Umbrel and see them alongside stuff installed from the official repository. Ok to require an external guy repo as upstream for this, but better to work entirely local.
Hello, do you have plans to interop with an established selfhosting distro and package scheme? Yunohost, Freedombox and Libreserver come to mind. If you'd rather go the containerized/virtualized way, there's a dozen or so distros based on Docker/LXC/K8S to make selfhosting easier.
I'm always happy that people are building stuff for selfhosting (though like others i'm skeptical of anything cryptocurrency-related), so please don't take it as a dismissal of your work, but i don't understand the appeal of building yet another solution and package format that's not interoperable with the others who have been out there for 5/10 years and provide good services to plenty of users already.
To be fair, apart from Dockerfiles there's not exactly any decent specification for declarative sysadmin (network ports, filesystem access..). The selfhosting field could certainly use a specification for selfhosted packages across distros, because the current situation places a strong burden on volunteer maintainers to keep up with updates.
Which ones do you have in mind? Would you count ChromeOS as one of those, too?
A few i had in mind (from my bookmarks): Cloudron, Sandstorm, HomelabOS, libre.sh, UBOS, Unraid, Helm, CasaOS, servers.coop's Capsul. In my opinion, in those virtualized solutions Sandstorm is the only one that's not a simple GUI for docker/LXC and had some actually interesting research going on (especially in terms of security). That's for generic selfhosting solutions, and i personally have no strong opinion about these as i'm more interested about bare-metal solutions that work on low-end hardware (Freedombox/Yunohost/LibreServer).
To this list you can add the free ansible/docker recipes used by friendly hosting coops such as webarch.coop or disroot.org. I'm guessing many other CHATONS.org/Libreho.st federation members also publish their recipes, but i wouldn't know for sure.
I don't count ChromeOS as anything as my understanding is it's just a web browser with a custom kernel? I may be missing something as i've never used it, and if i don't have the source code and/or have to pay Google a single cent to use it i most probably will never try it out.
Personally, when it comes to desktop virtualization, i'm very happy with QubesOS. It's not designed for graphics performance, but it's to my knowledge the only distro providing decent security for multi-VM graphical workloads, and their research keeps going!
Encouraging usage of privacy enabling services by default is good.
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.