Hello John Moser Yes, there are several ways to provide environment specific configurations. Docker and Axon.ivy offer many capabilities of parameterization for different environments. The difficulty is to decide which methods or mix of methods fits best for your projects needs. One could either: 1. mount different configuration files (like `ivy.yaml`, `app.yaml`, etc.) per environment into the container. I think that makes sense if every stage (dev, int, prod) looks completely different and the resulting yaml files have almost nothing in common. 2. use environment variables to override parts of our configurations https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#configuration-override. This is recommended if you only want to override a few configuration values while most configurations in the yaml files are shared. 3. build an image per environment. could sound a bit strange. but use the capabilities of your container orchestration platform like in the first scenario you can provide different configuration files (like `ivy.yaml`, `app.yaml`, etc.). but you don't need to mount a volume at runtime. this will lead to immutable configurations that are only modifyable from within the container. the docker per env approach could look like this: ## acmeDockerfile FROM axonivy/axonivy-engine COPY --chown=ivy:ivy AxonIvyEngine.lic /etc/axonivy-engine-7x/ ... ## acmeProdDockerfile FROM acmeDockerfile COPY --chown=ivy:ivy ivy-prod.yaml /etc/axonivy-engine-7x/ivy.yaml ## acmeTestDockerfile FROM acmeDockerfile COPY --chown=ivy:ivy ivy-test.yaml /etc/axonivy-engine-7x/ivy.yamlConfigMap for Kubernetes https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/ you may also check how to handle passwords (secrets) in containers: https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#engine-configuration-docker

Hello John Moser Yes, there are several ways to provide environment specific configurations. Docker and Axon.ivy offer many capabilities of parameterization for different environments. The difficulty is to decide which methods or mix of methods fits best for your projects needs. One could either: 1. mount different configuration files (like `ivy.yaml`, `app.yaml`, etc.) per environment into the container. I think that makes sense if every stage (dev, int, prod) looks completely different and the resulting yaml files have almost nothing in common. 2. use environment variables to override parts of our configurations https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#configuration-override. This is recommended if you only want to override a few configuration values while most configurations in the yaml files are shared. 3. build an image per environment. could sound a bit strange. but like in the first scenario you can provide different configuration files (like `ivy.yaml`, `app.yaml`, etc.). but you don't need to mount a volume at runtime. this will lead to immutable configurations that are only modifyable from within the container. the docker per env approach could look like this: ## acmeDockerfile FROM axonivy/axonivy-engine COPY --chown=ivy:ivy AxonIvyEngine.lic /usr/lib/axonivy-engine-7x/configuration//etc/axonivy-engine-7x/ ... ## acmeProdDockerfile FROM acmeDockerfile COPY --chown=ivy:ivy ivy-prod.yaml /usr/lib/axonivy-engine-7x/configuration/ivy.yaml/etc/axonivy-engine-7x/ivy.yaml ## acmeTestDockerfile FROM acmeDockerfile COPY --chown=ivy:ivy ivy-test.yaml /usr/lib/axonivy-engine-7x/configuration/ivy.yaml/etc/axonivy-engine-7x/ivy.yaml you may also check how to handle passwords (secrets) in containers: https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#engine-configuration-docker

Hello John Moser Yes, there are several ways to provide environment specific configurations. Docker and Axon.ivy offer many capabilities of parameterization for different environments. The difficulty is to decide which methods or mix of methods fits best for your projects needs. One could either: 1. mount different configuration files (like `ivy.yaml`, `app.yaml`, etc.) per environment into the container. I think that makes sense if every stage (dev, int, prod) looks completely different and the resulting yaml files have almost nothing in common. 2. use environment variables to override parts of our configurations https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#configuration-override. This is recommended if you only want to override a few configuration values while most configurations in the yaml files are shared. 3. build an image per environment. could sound a bit strange. but like in the first scenario you can provide different configuration files (like `ivy.yaml`, `app.yaml`, etc.). but you don't need to mount a volume at runtime. this will lead to immutable configurations that are only modifyable from within the container. the docker per env approach could look like this: ## acmeDockerfile FROM axonivy/axonivy-engine COPY --chown=ivy:ivy AxonIvyEngine.lic /usr/lib/axonivy-engine-7x/configuration/ ... ## acmeProdDockerfile FROM acmeDockerfile COPY --chown=ivy:ivy ivy-prod.yaml /usr/lib/axonivy-engine-7x/configuration/ivy.yaml ## acmeTestDockerfile FROM acmeDockerfile COPY --chown=ivy:ivy ivy-test.yaml /usr/lib/axonivy-engine-7x/configuration/ivy.yaml you may also check how to handle passwords (secrets) in containers: https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#engine-configuration-docker

Hello John Moser Yes, there are several ways to provide environment specific configurations. Docker and Axon.ivy offer many capabilities of parameterization for different environments. The difficulty is to decide which methods or mix of methods fits best for your projects needs. One could either: 1. mount different configuration files (like `ivy.yaml`, `app.yaml`, etc.) per environment into the container. I think that makes sense if every stage (dev, int, prod) looks completely different and the resulting yaml files have almost nothing in common. 2. use environment variables to override parts of our configurations https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#configuration-override. This is recommended if you only want to override a few configuration values while most configurations in the yaml files are shared. 3. build an image per environment. could sound a bit strange. but like in the first scenario you can provide different configuration files (like `ivy.yaml`, `app.yaml`, etc.). but you don't need to mount a volume at runtime. this will lead to immutable configurations that are only modifyable from within the container. ## acmeDockerfile FROM axonivy/axonivy-engine COPY --chown=ivy:ivy AxonIvyEngine.lic /usr/lib/axonivy-engine-7x/configuration/ ... ## acmeProdDockerfile FROM acmeDockerfile COPY --chown=ivy:ivy ivy-prod.yaml /usr/lib/axonivy-engine-7x/configuration/ivy.yaml you may also check how to handle passwords (secrets) in containers: https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#engine-configuration-docker

Hello John Moser Yes. There Yes, there are several ways. ways to provide environment specific configurations. Docker and Axon.ivy offer many capabilities of parameterization for different environments. The difficulty is to decide which methods or mix of methods fits best for your projects needs. One could either: 1. provide mount different configuration files (like `ivy.yaml`, `app.yaml`, etc.) per environment by mounting the file in into the container. we I think that makes sense if every stage (dev, int, prod) looks completely different.different and the resulting yaml files have almost nothing in common. 2. use environment variables to override all parts of our configurations https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#configuration-override. this This is recommended if you only want to override a few configuration values.values while most configurations in the yaml files are shared. 3. build an image per environment. could sound a bit strange. but like in the first scenario you can provide different configuration files (like `ivy.yaml`, `app.yaml`, etc.). but you don't need to mount a volume at runtime.runtime. this will lead to immutable configurations that are only modifyable from within the container. you may also check how to handle passwords (secrets) in containers: https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#engine-configuration-docker

Hello John Moser Yes. There are several ways. 1. provide different configuration files (like `ivy.yaml`, `app.yaml`, etc.) per environment by mounting the file in the container. we think that makes sense if every stage (dev, int, prod) looks completely different. 2. use environment variables to override all of our configurations https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#configuration-override. this is recommended if you only want to override a few configuration values. 3. build an image per environment. could sound a bit strange. but like in the first scenario you can provide different configuration files (like `ivy.yaml`, `app.yaml`, etc.). but you don't need to mount a volume at runtime. you may also check how to handle passwords (secrets) in containers: https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#engine-configuration-docker

Hello John Moser Simply use your capabilities of your container platform. Yes. There are multiple ways to solve several ways. 1. provide different configuration files (like `ivy.yaml`, `app.yaml`, etc.) per environment by mounting the file in the container. we think that problem:makes sense if every stage (dev, int, prod) looks completely different. 1. build image per environment 2. provide different `app.yaml` per environment by mapping the file to the container 3. use environment variables to to override all of our configurations https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#configuration-overridehttps://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#configuration-override. this is recommended if you only want to override a few configuration values. 3. build an image per environment. could sound a bit strange. like in the first scenario you can provide different configuration files (like `ivy.yaml`, `app.yaml`, etc.). but you don't need to mount a volume at runtime. you may also check how to handle passwords (secrets) in containers: https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#engine-configuration-docker

Hello John Moser Simply use your capabilities of your container platform. There are multiple ways to solve that problem: 1) 1. build image per environment 2) 2. provide different `app.yaml` per per environment by mapping the file to to the container 3) 3. use environment variables to to override all of our configurations configurations https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#configuration-override also check how to handle passwords (secrets) in containers: https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#engine-configuration-docker

Hello John Moser Simply use your capabilities of your container platform. There are multiple ways to solve that problem: 1) build image per environment 2) provide different app.yaml `app.yaml` per environment by mapping the file to the container 3) use environment variables to override all of our configurations https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#configuration-override also check how to handle passwords (secrets) in containers: https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#engine-configuration-docker

Hello John Moser Simply use your capabilities of your container platform. There are multiple ways to solve that problem: 1) build image per environment 2) provide different app.yaml per environment by mapping the file to the container 3) use environment variables to override all of our configurations https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#configuration-override also check how to handle passwords (secrets) in containers: https://developer.axonivy.com/doc/latest/EngineGuideHtml/configuration.html#engine-configuration-docker