You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project currently requires a .env file for reading in configuration values, however this doesn't suit deployment onto Docker Swarm. It would be great if the application could read Docker Swarm secret and config values, and come with a provided stack file.
I'm currently trying to add this as a service to our existing swarm, however I am realising it cannot do this currently, and am still figuring out if this is useful feature to implement (would be happy to make a PR for it when I have time). Also need to consider running one off management commands in this environment.
Is this a feature you would be willing to add? Or is there a reason I haven't considered?
Extra context: In my situation I am adding this as a service behind a Traefik reverse proxy, so I believe there could be an eventual solution where only a stack YAML file is required (which I can version control) after the secrets and config values are loaded into the swarm (since Nginx wouldn't be required).
The text was updated successfully, but these errors were encountered:
Kia ora,
The project currently requires a
.env
file for reading in configuration values, however this doesn't suit deployment onto Docker Swarm. It would be great if the application could read Docker Swarm secret and config values, and come with a provided stack file.I'm currently trying to add this as a service to our existing swarm, however I am realising it cannot do this currently, and am still figuring out if this is useful feature to implement (would be happy to make a PR for it when I have time). Also need to consider running one off management commands in this environment.
Is this a feature you would be willing to add? Or is there a reason I haven't considered?
Extra context: In my situation I am adding this as a service behind a Traefik reverse proxy, so I believe there could be an eventual solution where only a stack YAML file is required (which I can version control) after the secrets and config values are loaded into the swarm (since Nginx wouldn't be required).
The text was updated successfully, but these errors were encountered: