[-] boydster@sh.itjust.works 6 points 2 weeks ago

"Life is what happens to you while you're busy making other plans"

  • John Lennon, Beautiful Boy

And unbeknownst to me until I went to check to see if I was right about the origination (I wasn't), "Life is what happens to us while we are making other plans"

  • Allen Saunders, Readers Digest, January 1957
[-] boydster@sh.itjust.works 4 points 2 weeks ago

Wouldn't ya know it, he had a bad time

[-] boydster@sh.itjust.works 4 points 3 weeks ago* (last edited 3 weeks ago)

Because they are, for some baffling reason, deciding proactively to ruin the peanut butter after having blended it into smooth, creamy perfection! Then they have the gall to place it right next to the good stuff, likely with intent to fool unwitting passersby into bringing it home with further hopes that the children who have never tasted smooth peanut butter and fall victim to experiencing the crunchy version as their initial exposure will be hooked on the worse version for the rest of their lives.

If that's not malice, I don't know what is.

(Really heavy /s, just in case)

[-] boydster@sh.itjust.works 6 points 3 weeks ago* (last edited 3 weeks ago)

So it's not laziness, it's maliciousness?

[-] boydster@sh.itjust.works 6 points 1 month ago

And this is after he told advertisers to "fuck off" if they didn't like how he was doing things at twitter

[-] boydster@sh.itjust.works 73 points 1 month ago

How do they work?

[-] boydster@sh.itjust.works 1 points 1 month ago

Truly one of the latter day saints

[-] boydster@sh.itjust.works 2 points 1 month ago

I truly wasn't trying to disparage the source, it was just phrasing that jumped out at me as being a little off

[-] boydster@sh.itjust.works 5 points 1 month ago* (last edited 1 month ago)

At least one woman and several people...

I clicked the article to double check and sure enough, it's still there. I'm sure it's meant to enhance the perceived seriousness of the attack ("won't someone think of the women and children? Look! They hurt one!"), but it reads more like "one non-person, not understood to be pregnant at this time, and several actual human beings..."

[-] boydster@sh.itjust.works 13 points 1 month ago

But will you try actually installing the update on a machine or 50 to see if you bork things horrifically?

Crowdstrike: "We are really focused on unit testing right now"

I probably misread it, don't mind my grumbling, rabble rabble rabble

27
submitted 6 months ago* (last edited 6 months ago) by boydster@sh.itjust.works to c/linux@lemmy.ml

After seeing someone else posting their struggles with getting Docker running on their system, I thought I might share my process for setting up new Docker nodes. I don't make any representations about my way being the right way, or the best way, but this way has been working for me. I have been playing around with a swarm, but if you aren't setting up a swarm you can just omit the swarm commands and some of the firewall allows (keep what you need open, obviously, like 22 for SSH if you're using it). Similarly, if you aren't connecting to a NAS, you can leave out the part about mounting external storage.

# new Docker Swarm node setup from fresh Debian Netinst

# as root, all nodes
apt install sudo
usermod -aG sudo [user]
logout

# as [user], all nodes
sudo apt update
sudo apt upgrade -y
sudo apt install fail2ban rkhunter ufw unattended-upgrades ca-certificates curl -y
sudo ufw allow 22 
sudo ufw allow 2377
sudo ufw allow 7946
sudo ufw allow 4789
sudo ufw enable
sudo install -m 0755 -d /etc/apt/keyrings
sudo curl -fsSL https://download.docker.com/linux/debian/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc
echo \
  "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/debian \
  $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \
  sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt update
sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin -y
sudo usermod -aG docker [user]

## Shared Storage Stuff, all nodes ##

nano ~/.smbcredentials
# paste the following:
#   username=[cluserUser]
#   password=[clusterPW]
#
# add mount point for shared storage
sudo nano /etc/fstab
# add the following to the bottom:
# /[NAS.IP.Address]/[ClusterStorageFolder]/ /home/[user]/share cifs credentials=/home/[user]/.smbcredentials 0 0

# on main node only
docker swarm init --advertise-address 
  #  copy the join command, we'll need it next

# on any additional nodes, paste the command copied above
docker swarm join [...all the rest of the command...]

# for each docker container, on any manager node
mkdir ~/share/[serviceName]  
cd ~/share/[serviceName]
  #  copy relevant compose.yml into the folder
  #  if necessary, also create any needed directories
docker compose up -d
docker compose down
docker stack deploy -c compose.yml
12

Just saw these new HoMe boxed sets are coming out, with the first set releasing in November

14

Credit: TimeMaps

As part of a personal educational journey, I've been exploring early human cultures. There are a lot of great websites I've encountered along the way, but this one had escaped my radar until yesterday.

I grabbed the map portion from a series of posts they had about early farming and strung them all together into a gif so I could visualize it better for myself, and it ended up looking pretty neat so it seemed crazy not to share it.

The green parts of each slide show you where the farming was happening at the time. The first slide represents 10000 BCE, and each slide after is dated 1000 years further ahead in time, all the way up to the last slide at 3000 BCE, as outlined by the TimeMaps folks.

view more: next ›

boydster

joined 1 year ago