portainer will not start the resourcespace as a stack without some small modifications.
-
environment variables:
https://docs.portainer.io/user/docker/stacks/add#option-3-git-repository
You could use environment variables to define the listening port, and the database connection parameters. Especially the port, as portainer will likely refuse to start the stack because it's coded to 80, and doesn't give you the ability to change it.
-
config files:
pull 17
I can see this is already a pull request. Without this, the config file is hidden away and difficult to modify. We chose to modify it by adding an extra volume with the config inside it, but could just as esily used the filestore volume already mapped.
portainer will not start the resourcespace as a stack without some small modifications.
environment variables:
https://docs.portainer.io/user/docker/stacks/add#option-3-git-repository
You could use environment variables to define the listening port, and the database connection parameters. Especially the port, as portainer will likely refuse to start the stack because it's coded to 80, and doesn't give you the ability to change it.
config files:
pull 17
I can see this is already a pull request. Without this, the config file is hidden away and difficult to modify. We chose to modify it by adding an extra volume with the config inside it, but could just as esily used the filestore volume already mapped.