@atrilahiji that would be great πif you could shed some light on it. itβd be cool! I totally forgot about the self-host side of things earlier. π Added the note.
@jodumont yes. Samba is the only protocol on your list that is really made to be mounted locally. Personally I would try to avoid having to rely on php for access to remote filesystems (regardless of the protocol).
@humptydumpty I like your idea of educating the users on the login page itself. π You could also add something like This code protects your account even if someone stole your password. Or a better wording would make an impact, really!
@dfldadm I've built a couple custom apps that target Cloudron as a deployment platform, and published a sample of how to build/deploy to a Cloudron from GitHub Actions. Several of us would be happy to help you get that figured out if you run into any issues. In my experience, it's been roughly as easy as Heroku to operate once you get that initial setup done.
@plusone-nick it's really a feature that packagers can use to avoid writing extra code. Specifically it's for apps that have no user management. There is not user facing changes.
@girish also, I imagine if MailPile hadn't tried to make PGP easy as part of it the developer might not have burnt out and there might be a decent open source webmail app!
@mehdi MariaDB follows this as per Wikipedia: https://en.wikipedia.org/wiki/Business_models_for_open-source_software#Delayed_open-sourcing
It's even okay if the delayed open-source release is restricted to individuals and not corporates - to protect the revenue stream. But we must find a way to direct our resources towards improving public and community goods.
@jdaviescoates I took a quick look at some video tutorials, but I didn't see how Keycloak would be able to log the user into other applications without having said application specifically implementing the Keycloak integration.
You've already looked into it more than me. I guess Indiehosters have implemented Keycloak integration into the apps they've integrated in their Liiibre service (perhaps they maintain forks or something, or have contributed upstream).
Long and rocky experience tells me with operating systems to stay a year behind.
Especially when security patches are normally supported for 5 years and optimisations are usually all in the apps and service version updates within.
Let others do the OS battle-testing for a year or play with it for non-critical systems, but life's too short to be on the bleeding edge in production.