Hi @RGJ,
Just one follow-up thought:
The corner case, where hard coding the container identifiers (be it container id, name or both) as yml env vars may not work, is with Docker Swarm or Kubernetes (examples); because when containers are dynamic based on load and / or fault, hard-coding env vars in yml will not work (I assume, but have not yet done it to speak with authority on the subject); but I’m willing to go with the “simple approach” for now (env vars in yml).
Anyway, I have not yet deployed Discourse with Swarm or Kuber, so my plan was to cross that bridge when I come to it later ![]()
I have given a lot of thought to this, and that is why I have decided the best route at this point in time is to go with Discourse environmental vars hard-coded into the yml file(s).
It should be a relative easy task to take these env vars, as site settings, and display them on the admin backups page per my quick little mockup:
