Sure, it’s just easier for me to tweak in Portainer. But, yeah. There are many ways to skin the cat.

Welcome! Good to meet you.

Most of those containers are probably grabbing more memory than they actually need.

It took a bit of trial and error with Portainer, but under Runtime & Resources, you can adjust the amount of needed resources:

• Shared memory size
• Memory reservation (MB)
• Memory limit (MB)
• Maximum CPU usage

Thanks for the tip. I’ll definitely check it out

This is how I use front end apps. Other than the data contained in the posts, I have no interest in Insta, FB, et al. Similar to how I use RedLib for Reddit because, despite Reddit turning into a cesspool, there are still some great technical subs that contain valuable info. Interacting on Reddit tho, is a hard pass.

My docker files, configs, and volumes are all kept in a structure like:

Over the years, I have gravitated to keeping docker compose, configs, et al, in structured directories in lieu of docker just splattering the HDD willie-nilly, with configs anywhere and everywhere. It sure makes problem solving much easier when you can go directly to where each component is instead of spending 30 minutes trying to locate where docker put everything.

Out of curiosity, how are you doing the drive imaging?

I wrote a script that is fired by a cron job once a month:

sudo nano /usr/local/bin/backup_drive.sh

# Directory to store backups

BACKUP_DIR="/mnt/myhdd"

# Drive to backup

DRIVE="/dev/sdX"

# Create a timestamp

TIMESTAMP=$(date +"%Y%m%d")

# Filename for the new image

NEW_IMAGE="$BACKUP_DIR/my_drive_image_$TIMESTAMP.img"

# Create the image

sudo dd if=$DRIVE of=$NEW_IMAGE bs=4M status=progress

# Keep the last 3 images

ls -tp $BACKUP_DIR/my_drive_image_*.img | grep -v '/$' | tail -n +4 | xargs -I {} rm -- {}

Make the script executable:

sudo chmod +x /usr/local/bin/backup_drive.sh

Create Cron:

sudo crontab -e

0 3 1 * * /usr/local/bin/backup_drive.sh

Verify cron:

sudo crontab -l

I’m sure it could be written differently or that there is a better way to do the imaging, but that is the extent of my notes, and it works for me. As with any code you find on the internet, it is wise to evaluate before dropping on a production server.

one of the great aspects of the open source community.

Absolutely. I was quite humbled.

Well, there is Mixarr. I believe it downloads and gives recommends. However, there is also a version if you just want recommendations: Mixarr Unleaded which the dev graciously modified just for me apparently. Thanks aquantumofdonuts!! So I feel obligated to recommend the unleaded version of Mixarr.

lol indeed

Im tired of doing unending infa buildouts.

I have my server pretty much set the way I want things. Now, I do tinker a lot. I enjoy the tinkering because I’m learning and to me, it’s fun. It’s a very useful hobby. The tinkering, however, happens either on separate, local machinery, or on my test VPS. Not on my production server.

But I feel ya. Once you have something the way you want it, it works for you, and matches your flow, no need to constantly reinvent the wheel.

blog.elenarossini.com

Is this your blog? You take nice pictures. Always wanted to get into photography.

Yunohost has come a long way, and as far as I know, has the biggest app catalog for it’s class. I recommend it for people who are just starting their self hosting journey, but there’s no reason to jump ship after you’ve got some experience.

In addition to daily backups, once a month I image the drive. I wrote a simple script triggered by a cron job to image the drive to a NAS backup. The daily backups go to 3 different offsite storage facilities, and two go to separate NAS drives. All drive images are kept both local and off premise as well. So, for individual files, etc, I can restore them from the daily backups. If the wheels fall off, I can restore the whole drive from an image. Might be a bit over engineered but I’ve been caught a few times and so I just decided that won’t happen again.

This is the way with a lot of tech. Someone comes up with an ides, tries to build it and make it successful. When the money starts getting tight, they sell it to a larger company. Usually by the third round, it becomes successful.

netstat -lpn | grep 8080

That’s a bit cleaner than sudo lsof -i :8080. It always amazes me tho, how many different commands/ways there are in Linux to get to the same spot.

No worries mate.

I don’t run Headscale but it appears that there is a conflict.

Who is using port 8080: sudo lsof -i :8080

Have you tried either changing Crowdsec’s port or Headscale’s port?

Change Crowdsed’s port

Change Headscale port:

/etc/headscale/config.yaml

headscale:
  listen_addr: 127.0.0.1:8081

sudo headscale serve

Hello, My Name Is

1975: An artist by the name of Labi Siffre released a track called ‘I got the…’, a song about his partner Peter Lloyd. Labi Siffre is the real Slim Shady.

I mean, of course Bezos wants to rent you a cloud PC. Bezos would sell your shit back to you if he thought there was a market. Hell, I’d sell your shit back to you if I thought you’d buy it. When I see headlines like these I think ‘Well…duh’.

Most people don’t need a machine, they just need a thin client

Amazing how we’re come full circle