Infrastructure nerd, gamer, and Lemmy.ca maintainer
Picking obscure ports doesn’t really add security, are you using authentication?
That’s correct. You’re telling docker to bind to that specific network interface. The default is 0.0.0.0 which listens on all interfaces.
FYI all mod actions should show up, but if a post has been “purged” (completely deleted from the lemmy db) then it also disappears from the modlog.
Very safe unless you attach razor blades to the blades.
Most small DC motors don’t have enough power to break the skin
It’s not as big a risk as this person is making out. If you’re playing with low current microcontroller stuff, there’s virtually no risk. At most you’re gonna let the magic smoke out of a chip, not start a fire.
If you start getting into stepper motors and things like that, sure, but that’s a long ways from where you are today.
Find a project and make it. Maybe something off adafruit? https://learn.adafruit.com/
Pick up a pinecil for your first soldering iron.
She’s baiting the crap out of him, and he keeps taking it before going off rambling. It’s great.
Please America I hope the people that need to watch this, are doing so.
https://github.com/containrrr/watchtower is a bit cleaner than that
Bro, just docker-compose pull && docker-compose up -d
I’m appreciating how rapid the releases have been coming lately.
You could just swap the two disks and see if it follows the drive or the link.
If the drive, rma it. I don’t put a lot of faith in smart data.
Usually means a failing drive in my experience.
Rotate your phone 90 degrees clockwise. Problem solved.
Nothing else that immediately comes to mind, it was like 20 years ago.
Two big ones in my younger days:
Alt tabbed one too many times, clicked drop database, clicked ok, realized I’d just deleted the live user database for America’s Army. Thankfully it was the east coast site and west coast was the primary, and it was only one way replication. We shut down east coast auth and rebuilt the secondary.
Someone distracted me while typing in a vlan command on a switch, I hit enter without double checking, took out our fiber between two datacenters in the middle of a move. Took me 15 minutes to run to the DC, plug in a console cable and fix it. Took all of our customers out.
The file handle of the directory changes when you mount the nfs on it, and docker is still looking at the old file handle.
It’d probably work if you mounted nfs to a folder inside that one, or moved your docker mount one level up.
Otherwise you’ll need to get your container to restart after the mount is attached. You could do this with a health check for the container that checks the files are there, and restart the container if they’re not. Or you could just fix your boot order and set nfs as a dependency for docker.
Would be better if you made it “a joke about maize”
They want it as a word doc so they can edit it and fuck with it before passing it along.