+1 for SingleFile
I recently tried LinkWarden, Linkding and Archivebox for making offline copies. They all had the same issue of running in to a Captcha or login wall for the sites I wanted to capture.
SingleFile to the rescue, as it uses your current browser session as a logged in and verified human.
Linkeding allows you to upload the singlefile html file attached to it link, but I didn’t see such an option for Linkwarden.
I hadn’t considered giant data sets, like Jellyfin movie library, or Immich photo library. Though for Jellyfin I’d consider only the database and config as “Jellyfin data”, while the movie library is its own entity, shared to Jellyfin
How does this work? Where is additional space used for cache, server or client?
Or are you saying everything is on one host at the moment, and you use NFS from the host to the docker container (on the same host)?
This has been my thinking too.
Though after reading mbirth’s comment I realised it’s possible to use named volumes and explicitly tell it where on disk to store the volume:
volumes:
- my-named-volume:/data/
volumes:
my-named-volume:
driver: local
driver_opts:
type: none
device: "./folder-next-to-compose-yml"
# device: "/path/to/well/known/folder"
o: bind
It’s a bit verbose, but at least I know which folder and partition holds the data, while keeping the benefits of named volumes.
KDE Connect also works on Gnome, Windows and Android. I can’t recommend it enough. Transfering a single image from phone to PC is instantaneous
GUIs can be very good for getting started and learning concepts though. Much more “discoverable” and can allow for quicker iteration.
Then when learning the “proper” command line tools, the process should be easier as one already knows the concepts and terminology, and can concentrate on just the tooling.
Regarding mini PCs; Beware of RAM overheating!
I bought some Minisforum HM90 for Proxmox selfhosting, installed 64gb RAM (2x32gb DDR4 3200MHz sticks), ran memtest first to ensure the RAM was good, and all 3 mini PCs failed to various degrees.
The “best” would run for a couple of days and tens of passes before throwing multiple errors (tens of errors) then run for another few days without errors.
Turns out the RAM overheated. 85-95 C surface temperature. (There’s almost no space or openings for air circulation on that side of the PC). Taking the lid off the PC, let 2/3 computers run memtest for a week with no errors, but one still gave the occasional error bursts. RAM surface temperature with the lid off was still 80-85 C.
Adding a small fan creating a small draft dropped the temperature to 55-60 C. I then left the computer running memtest for a few weeks while I was away, then another few weeks while busy with other stuff. It has now been 6 weeks of continuous memtest, so I’m fairly confident in the integrity of the RAM, as long as they’re cold.
Turns out also some, but not all, RAM sticks have onboard temperature sensors.
lm-sensorscan read the RAM temperature, if the sticks have the sensor. So I’m making a Arduino solution to monitor the temperature with a IR sensor and also control an extra fan.