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.
Is there anyone out there running an AMD 5650GE based system running Linux or BSD?
Can you tell us your CPU and GPU idle power numbers as displayed in btop?
Maybe this is an "easy button" of sorts to reduce power on an existing AMD AM4 system without the going through the machinations of new mobo, ram, etc., etc. Get most of the way there?
#Linux #RunBSD #AMD #5650GE #PowerConsumption #Power #HomeLab #SelfHosting #SelfHosted #SOHO
Is there anyone out there running an AMD 5825U based system running Linux or BSD?
Can you tell us your CPU and GPU idle power numbers as displayed in btop?
#Linux #RunBSD #AMD #5825U #PowerConsumption #Power #HomeLab #SelfHosting #SelfHosted #SOHO
The convenience of synchronisation between devices are the most common argument that I hear from friends why they are so invested in the respective walled gardens. But the same advantages can be obtained with old well-tested and open standards. Example: get an SMS with e-mail, add it to contacts and then have it autocomplete in @thunderbird@mastodon.online connecting to whichever mail provider your heart desires, thanks to the magic of CardDAV and IMAP. No need for Giant Mail :)
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.