Mankeulv Prerifarkas@lemmy.latrans.cloudtoLinux@lemmy.ml•Filesystem Hierarchy Standard - Reference Poster / Cheatsheet [Dark mode in details]
7·
7 months agoNicely done! Do you perchance have any hi res version?
Nicely done! Do you perchance have any hi res version?
sniffff They grow up so fast… :')
I also have a QNAP and I have no problem mounting the SMB shares into a folder in the filesystem. If you ever want to try again, feel free to touch base with me and I’ll share my config.
Second this, it’s my daily driver on android to control my qBittorrent instance, and so far I haven’t missed any kind of functionality, it just does everything I need.
Aw yissss… About time!
Holy… This is one of the most deranged things I’ve ever read…
I had to stop reading 3/4 of the way, I couldn’t take the craziness anymore.
You cannot reference a part of a docker-compose file from another, but you can have an .env file alongside them where you can declare variables in the format NAME=VALUE, and reference that in the dc files with ${NAME}, assuming your dc files reside alongside each other (with different names) and the .env file itself. I have done this before.
I cannot say if that will work for your use case, as I haven’t tried to use the same docker volume in different containers. I don’t even know if that is possible, given the possibility of conflicts if both containers tried to access the same files, something to test out, for sure.