fix: expose the version as an environment variable in the context

[varl]

Relates to: https://github.com/amcgee/dhis2-backend/pull/2

No longer coupled to the dhis2-backend PR.

[amcgee]

Very cool that this enables support for multiple instances behind a gateway! See my comment on the companion pr for concerns about tight coupling.

One question which may be important - do we want to support arbitrary context paths per cluster, or would it be sufficient to support a singular "cluster" gateway which proxies to multiple "versioned and named" clusters behind it. I.E.

d2 cluster config --port 8080
d2 cluster add --version dev --name mydevinstance
d2 cluster add --version 2.32 --name latest

(or something better with nicer commands)

Could result in a single gateway pointing at multiple clusters behind-the-scenes, so you could access localhost:8080/mydevinstance and localhost:8080/latest. This is a little less flexible but a little more controlled than allowing arbitrary context specification.

[varl]

Could you take another look at this as well as https://github.com/amcgee/dhis2-backend/pull/2#issuecomment-490872497? They should be less coupled.

[varl]

One question which may be important - do we want to support arbitrary context paths per cluster, or would it be sufficient to support a singular "cluster" gateway which proxies to multiple "versioned and named" clusters behind it. I.E.

I'm not exactly sure how this would work in practice, for example, I would still have to put an nginx reverse proxy in front of that "singular gateway" in order to serve the other sites I have on the same server.

But maybe --name is better than --context, as a different docker-compose repo might want to use the name environment for something else.

[varl]

I pulled out the single port cluster discussion to a separate issue.

[varl]

This only exposes the version as an environment property now.

[amcgee]

LGTM!

[dhis2-bot]

🎉 This PR is included in version 1.0.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀