The sign-in experience is where you’re going to get a lot of friction. Your users are going to need your server address. They’ll have to log in to devices with username/password including TVs unless they have signed in once already somewhere else on the network like a desktop. Then you can set up an Easy PIN code or use Quick Connect, but those are hidden behind the user settings menu.
Are you still using it? I went through many deployments before I finally thought I had it settled.
At the beginning of the pandemic I looked into ways to de-Google and found Nextcloud. It wasn’t the easiest thing to start with, especially for a novice, but I had the time and the hardware, and I’m the type to not mind jumping into something difficult if it means solving a specific problem. I then found out about Bitwarden and had a great experience setting that up. After that I was confident enough to try hosting anything I could find. It’s been good times ever since 😀
This is extremely valuable, thanks for this!
As a general question, why did you decide to use a single postgres container for multiple services instead of multiple, stack specific containers? When I first started working with containers I considered your scheme for the sake of minimalism, but didn’t want a single container to bring down multiple unrelated services. I also had the resources to accomodate the redundancy.
Is this a repost? I’ve seen this exact same post somewhere.
Anyway, SimpleX may not be decentralized OOTB, but can be made to be since their relays are self-hostable. It should be as simple as spinning up an instance and changing the url in app.