Always remember: RAID is not a backup.
Having only one backup and the server dying means you now have no backup, therefore the 3-2-1 scheme for backups is worth looking into.
That depends a lot on what you're hosting resp. if the mobile apps are using Google's/Apple's messaging/notification services.
Not sure if it makes things easier than your current setup, but take a look at Mediathekwebview.de
Running NC on the same instance for the last 4 years on docker. Both point versions and major version upgrades work fine, as long as you take care to check for 3rd party app compatibility.
Not running "latest" and not auto-updating helps.
Hetzner
Use the web console and check which IP the machine actually has.
You can use -f /path/to/compose.yaml to call it from wherever you like.
Is he going to offer miniature submarines and call people pedos again?
If you're already familiar with it and can maybe even reuse some compose files, it's definitely worth it. Even on a Pi.
What did I do wrong
I was configuring some network stuff
Unless you knew exactly what you were doing, chances are good you're currently without a working network connection, I.e. the machine is likely running, but not being able to connect to it will have the same effect as it being powered off.
Unfortunately the steps to fix that are even "worse" than for a machine that's simply powered down. How long will it be until you're back in your home?
how do y’all handle rebooting your bare metal when you don’t have access to the physical server atm?
I simply don't. At least not those that aren't covered by idrac etc.
The official NC docker container uses the "www-data" internally to run the services. This will get important if you ever want to run tasks via "docker compose exec".
Have a look at kimai.org
The have a self-hosted option and apps (didn't test those though).
Which means it's likely a US-focussed scenario.
Je nach Phase und Aufgaben alles zwischen 10 und tatsächlich 100%. Letzteres meistens wenn Schulungen anstehen.
Es ist ein himmelweiter Unterschied zwischen Haschisch rauchenden Personen und fröhlich feiernden Wiesn-Besuchern”,
Das stimmt schon, aber eher andersrum als die Wirte das gemeint haben.
That was the first one I tried. Sounded fantastic in theory, didn't work out for shit. For some reason the sensor dropped out constantly. The USB PSU bottom was nice though, no batteries to change.
Those fucking religious nutjobs...
Märchenbuch-Fanatismus machts möglich.
As previously discussed here https://feddit.de/post/1285536 , I am trying to properly decommission my private instance. My main issue: even though I unsubscribed from all communities, the server still gets a lot of POST requests with likes, comments, etc. So how do I tell all the instances to stop sending announcements? I also don't want to go the hacky way of bogus DNS entries, as that won't be good for the other instances. This also continues if I simply shut down the stack, just resulting in a lot of 404s.
Is there a manual for this I missed in all the googling?
While it was an interesting and sometimes confusing experience setting up and running my own Lemmy instance (looking at you, 20 character limit on federation URL), I think it's not worth it.
Now the time has come to decommission the service, is there a proper way to do that? I don't mean the local part, that's on docker and gone with 3 lines of bash input. I mean the overall process. How do I tell other instances that mine won't be available any longer? I noticed a constant stream of federation pushes, even with everything deleted and purged. Shutting down the instance won't help either, the requests will simply 404 then, but won't stop, which in itself is only logical. Has anyone done this before and could shed some light on this situation?
Edit: So I played around with the logs some more, there seemed to be an issue with communities that are on "subscription pending". I restored an older database which had all the entries, removed any federation restrictions and tried again from scratch, leaving and joining again until all communities were properly subscribed to.
Then:
- Unsubscribe
- Remove
- Purge
Just to be sure the entries are gone. As of 15 minutes ago, Traefik hasn't logged a single connection to my instance.
Edit2:
Turns out that wasn't it. My instance is on 0.17.4, and even with every community unsubscribed and purged, I'm being hammered by lemmy.world activity_pub events. The formatting is also different, I think that's because they moved to the 0.18 RC stage. So it looks like something somewhere didn't get the unsubscribe announcement.
Edit 3:
So I tried moving to 0.18-RC. Which now means lemmy.world is trying to push the inbox to the frontend? WTH...
After running HA for 2 years and tinkering with the stuff I already had, it was time to extend the little machine via Zigbee. I got an Aqara Temp/Humidity/Pressure sensor, which in itself works fine. It just chewed through 30% of battery in 4 days. Now that might be an issue with placement and signal strength (basement through 2 floors), but it doesn't bode well unless it "levels out" at some point.
Which brings me to my actual question: does anyone know any such sensors that are wall-powered in any way? Something that can be plugged in and "forgotten" about?