Mankeulv Prerifarkas

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.

sniffff They grow up so fast… :')

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.

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.

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.