Back to #dockge from #arcane as a web UI for docker compose management. Arcane has more bells and whistles (and required clicks) than I need, and the dockge repo seems to have become active again https://github.com/louislam/dockge also became a sponsor of the project while at at it. #SelfHosting

If you’re a self hoster or interested into getting into #selfhosting have a look at this series by @colocataires https://blog.colocataires.dev/

It’s very well written, informative and has a few projects listed I wasn’t aware of yet.

My current #selfhosted stack, will update this as I go along: https://notes.zef.pub/self-hosted-stack

#selfhosting

Most interesting alternative to Dockge I've seen so far is Komodo: https://komo.do/ will install it a bit later.

#selfhosted #Selfhosting

#Selfhosted and #Selfhosting people, what your current go-to for web-based docker container management? I've been using #dockge and I like it, but it seems nothing much is happening there (last commit 8 months ago). I tried Arcane, but... it's a bit... arcane, I liked dockge's simplicity more. #portainer seems to have gone enterprise and is likely to get more "enshittified" over time. So what do you all use?

Step 1 of my #SelfHosting disaster planning (my server sounds like it's about to die) is to go through all VMs and document what's there in @silverbulletmd:

* Name of the VM
* IP
* Login method (primary account)
* What's running there
* Key configuration paths and config files

Should have done this from day one, because you forget a lot after years. Now it's like #SelfHosted archeology.

Home server started to make weird noises. Enough to have to switch it off for the night. This is one of those times where I’m less excited #selfhosting a bunch of stuff. @silverbulletmd of course still works (#OfflineFirst), but a bunch of home automation won’t, no miniflux, no linkding, no EV charging (don’t ask). I suppose this is what I’ll be doing tomorrow…

New blog post!

A postmortem on how my VPS got infected with a crypto miner through, probably, a vulnerability in a docker container. And that has shown all things I have been doing wrong with administrating my server and self hosted services.

With many thanks to @louis @agturcz and @cichy1173

https://stfn.pl/blog/88-i-got-hacked/

#blog #vps #selfhosting #umami

I’m convinced 99% of people who give NextCloud a try give up on it after a few hours or couple of days. I certainly did.

It’s incredibly cumbersome and heavy for most things it’s trying to replace.

#SelfHosted #selfhosting

In the past few days I’ve seen talk about RAM prices shooting up due to demand from big datacenters.

Today I read that a historic brand like Crucial - I own plenty of their hardware, including SSDs - is dropping consumer products to focus on gear for those same datacenters.
The result (or maybe the intention?) is to push people away from self hosting, undermine the OwnYourData idea and make everyone depend on huge datacenters for life.

So much for owning your data.
So much for decentralisation.

Because taking down one giant datacenter is far easier than taking down thousands or millions of individual nodes.

Friends and colleagues, don’t trade your freedom for a bit of convenience. Once you give it away, getting it back is very hard.

Always Own Your Data.

#OwnYourData #SelfHosting

#selfhosting folks:

How, really, louder are ironwolfs 10tb+ compared to we red 6tb?

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

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.