

If you using bind mounts - you are using dockers in wrong way. Use named volumes.


If you using bind mounts - you are using dockers in wrong way. Use named volumes.
Woodpecker. No BS CI which can be attached to pretty much anything. It just need a webhook and way to pull your project.


This is wrong. Need to mourn and continue,not show weakness.


It seems my cat is sleeping on duty :-) ( he is 17 y.o. so it is excusable ) or I have brave and very hungry possums around.


You managed to grow nasturtium? Probably in house. All my attempts ends same way, it got eaten by possum. It seems to be too tasty.


Is there a way to check whether I sent her a message? I’m sure I did, but I can’t find it anywhere.


If you need something which can withstand some bitrot on single drive, just use par2. As long is filesystem is readable, you can recover files even if bit of data get corrupted


It means you published 8080. Just stop doing it. nginx can reach that container via internal network (assuming they are on same network). Publishing docker-compose would help.


Just a hdd in usb caddy? IMHO good enough for 4 tier backup.


It is corporate takeover, why be so surprised?


just a normal PC? Streaming should work in a browser.


And it is good thing. Corporate takeover of USA will not help anyone but billionaires.
Just a folder + syncthing. no extra infra is necessary + easy to backup.


With raid 10 - i would not risk it . With RAID6 ( obviously not on BTRFS) it is fair game if you have solid return policy for drives which are DOA. Go for SAS drives, they are cheaper (but generally hotter and nosier). And look for old-new-stock on specialized sites, no one in enterprise needs say 8tb drives, so they selling them cheap at times.
Get drive, connect , run long smart self-test ( for 18tb it is probably take a day). If it passed you are reasonably sure that it will not die soon. And keep running these test regularly, as soon as they start failing, replace.
If you care about security you build it is own. No need to trust random dude in the internet. After all It just fire and forget. Copy whatever “code” is used to build container you are after, verify it once and than just rebuild it periodically to pull patches from more reliable sources.
Docker security is a joke, no need to make it worse.