Nicely done! Do you perchance have any hi res version?
mankeulv
joined 1 year ago
sniffff They grow up so fast... :')
Welp, time to start looking for alternatives...
Can't blame the dev for wanting to cash out on his work, but I am not going to keep using apps that will get ridden with ads and trackers.
I believe you meant "excellent"...
Autocorrect, amirite?
In regards to productivity, you could also take a look at Get Things Done or Bullet Journal as time/task organization frameworks, or Zettelkasten if you need data/knowledge organization.
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.
Aw yissss... About time!
I'm running all my services behind Traefik, which handles getting a wildcard cert for all my (sub)domains with letsencrypt.
Once I figured out how to write the config properly, I haven't had to touch it again, pretty happy with the result.
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.
I second OVH, been using their services for the best part of 2 decades now, and I can't see myself migrating out unless something big happens.
I really love the ease of editing DNS zones and the free dynamic DNS with your domains. A self-hoster delight, for sure.
To add to this, my country has been rolling out 10Gbps U/D FTTH for 35€/Month for a while, and even rural areas usually have at least 500Mbps U/D, all of it uncapped.
Gotta say, more than a decade ago ISP's tried to implement data caps on home internet, and it failed spectacularly.
I weep for our American brethren, may they find a way out of the hole they're in...
view more: next ›
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.