You could try using bindfs to spoof the original user id and then chown the whole drive after successfull mounting (i’m a noob, just my understanding of the issue, don’t know if that’s really possible)
You could try using bindfs to spoof the original user id and then chown the whole drive after successfull mounting (i’m a noob, just my understanding of the issue, don’t know if that’s really possible)
The good thing about Linux is, it’s not very ressouce demanding. If you pick the xfce version of Mint, you can get away with 4GB of RAM. But you won’t have that much fun coding as soon as you start something more ressource heavy (big data sets, ML, …) so this depends a little in which direction you want to go. However see if you can find something used, preferably something you can open from the back side to upgrade components like SSD and RAM (cheaper than buying higher specs)
Sorry, I meant risk taking not averse (not my 1st language) Regarding the bugs, they get usually fixed within days
*10.9 if not latest. For the risk averse folks out there, check out https://github.com/containrrr/watchtower I just let it run every night, so far w/o problems
I struggled with Kubuntu as newbie (coming from Windows) - Mint was easier for me and I sticked with it (Cinnamon in my case, but my laptop is more powerful)
Most of my PRs are fixing typos in the Readmes 8) It ain’t much, but it’s honest work
Okay, let’s play this game :D Mint, because it’s frickin easy and fulfills all my needs while being stable enough for my work laptop
a typical (full subtitle) .srt file for a movie is like 100-200 kb - still not much, but 5 is a little off
I know and I tell her that, too - it’s just something to consider when calculating the wife approval factor
My gf likes to click on ad entries of Google searches - that doesn’t work
Not a single sidewalk is built to last the weight of a car. They are build as cheap as possible (sand bed + stones), because they are not supposed to get exposed to heavy loads. That’s why they are often in bad conditions, they usually don’t even have tree root protection, so they get regularly misformed from below and above
I’d recommend finding a tutorial for Docker+Portainer - Portainer is a container as well, which provides a web-gui to conveniently manage all your other containers (without having to touch the CLI ever again)
The Hacs Integration makes use of the device’s API - don’t know if it is their intended use of it, but it works
You can turn off the internet access at almost all Tuya devices by making use of the local tuya HACS add on in home assistant. Maybe that’s helpful for your research
Don’t worry, most of this is about learning :) You could also put Docker on the Linux, install Jellyfin as a Docker container, and only fore it up when you are using Jellyfin. It’s a little less convenient, than having it available all the time, but storing all media in H264 AC3 (most common video and audio codecs) costs a lot of storage (H265 and AV1 are far more efficient). Another pro of Docker is, when you decide to move your server, you just shut down the container, copy it’s data and start the container on the new device
You’ll have to keep in mind, that the pi is not really suitable for RAID and not at all for transcoding. The latter means if you have all your media in codecs your devices support, it’s direct play only, it will work, but as soon as you need to transcode, you will have a hard time
I’d go for the consumer case with as much drive space as possible, but in the end it’s up to your taste. With rackmount full professional server stuff, you have to keep in mind, it’s not only quite large in terms of space, but also noisy. This is something for the basement or something. Another option would be a mini pc like a NUC combined with a NAS - here is the limit the upgradability of the hardware. Like you can usually upgrade the RAM a little and the system drive, but that’s it. Especially for media stuff (Plex, Emby, Jellyfin) it can be interesting to have a dedicated GPU, like an Intel card, to have more transcoding capabilities. I’m currently running most things from a SFF PC, but also have a Pi and an old laptop in use for various tasks (main reason is lazyness to move the services to the SFF lol)
That’s the good thing about containers, that’s super easy. Just stop the container, move your folder to your desired location (e.g. /home/user/vaultwarden), change the path in your compose file (stack) (i.e.: /home/user/vaultwarden:/data/), redeploy the stack and that’s it :)
Ben phelp’s homepage (you can find it on github)
renderD128 (Intel dgpu) couldn’t be added to the container (linuxserver image). Will take a look later, when I’m home, to find the issue. But may take your time for the update and don’t yolo it like I did :)