m5l.eu is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
What top level domain do you use for your self hosted home services? I am considering .home or .lan.
I'm thinking of ways of making SilverBullet more accessible to the not hardcore #selfhosting crowd. Which of these options would you like more:
1. Fully hosted: essentially a SaaS offering: create an account online, we'll host all your content, you just access it from anywhere.
2. Internet tunnel: run SilverBullet locally on your desktop, access it via your browser (localhost), and optionally tunnel via a service to access it from anywhere (as long as your desktop is running).
3. Desktop app
| Fully hosted: | 18 |
| Internet tunnel: | 18 |
| Desktop app: | 29 |
Closed
My ISP was kind enough to give me a learning opportunity in how I can manage access to my homelab. While access to #selfhosting can't be in my place by definition, I can at least have it on a VPS from a local company to resist monopolies :)
I'm running Forgejo in a container now to isolate SSH access, but I also had it installed directly for some time.
This is what I use now, after #selfhosting Apache SVN, Perforce, Tuleap, RhodeCode, Phorge and Gitea so far.
Live location is very sensitive data, but #selfhosting the server with TLS and basic authentication gives me more privacy than the big tech cloud. And it only needed reading a bit of MDN and making a basic #Docker image based on #NodeJS
This time it's #Debian with #Docker. I used to avoid containers, preferring to run services directly instead. But setting up backups made me appreciate the separation between the application data in image and persistent state in mounted volumes. The final piece that convinced me is the ability to self-host my own container registry with @forgejo@floss.social
I'm doing the initial setup through #Ansible (learned from @notthebee@tilde.zone), but specific applications are managed via dockge. The ambition to do every adjustment through playbooks burns out really fast when working with a single instance.