Allow changing the name of the backend container. about grocy-docker

[max-tet]

The links feature was a great idea. I replaced

    depends_on:
      - grocy-backend

with

    links:
      - grocy-backend:backend

and it works as intended. Thank you!

[jayaddison]

Hi @max-tet - some observations, and then some ideas:

• nginx doesn't support reading the fastcgi_pass value from an environment variable - we could instead write a static value into each backend container image config.. but that would defeat some of the caching and assurance benefits of knowing that the containers are running from identical images, not to mention being ugly to implement.

• It sounds like what you want to achieve is the ability to run multiple instances of Grocy within a single Docker runtime, and the resolution of the backend name from each frontend node is causing problems here.

Could you let me know if either of these ideas appeal:

• Using the links feature of the Docker compose file to add a DNS resolution from grocy-backend:backend within the scope of grocy-frontend.

• Declaring separate Docker networks for each of the paired containers, and then specifying container_name: backend on each of the backend containers so that within that network it is known as backend and resolves correctly from nginx.

There could be other options I'm not considering here; further ideas (and/or further investigation of the environment variable idea if I've missed something there) welcome.