I have a set of stacks that all use the same compose.yaml template file, but with unique project variables. I've pulled this into komodo using "files on server" and it finds the compose and other files to show under "info", however the status stays as "down". Could the monitoring check evaluate the .env variable for the stack?
I set the stack's name in Komodo to "wp-abc" or whatever the ${PROJ} is for that stack.
See my compose file below.
Originally created by @LunkSnee on GitHub (Aug 31, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/790
I have a set of stacks that all use the same compose.yaml template file, but with unique project variables. I've pulled this into komodo using "files on server" and it finds the compose and other files to show under "info", however the status stays as "down". Could the monitoring check evaluate the .env variable for the stack?
I set the stack's name in Komodo to "wp-abc" or whatever the ${PROJ} is for that stack.
See my compose file below.
```
services:
wordpress:
container_name: wp-${PROJ}
image: docker.io/bitnami/wordpress:latest
volumes:
[...]
environment:
[...]
restart: unless-stopped
```
and the .env includes:
```
### PROJECT SETTINGS
PROJ=abc
[...]
```
Komodo should handle this edge case, but this case requires container name to be extracted from "docker compose config", which only happens when Deployed with Komodo. Can you try a single Re/deploy with Komodo, and see if this fixes this issue?
<!-- gh-comment-id:3240713690 -->
@mbecker20 commented on GitHub (Sep 1, 2025):
Komodo should handle this edge case, but this case requires container name to be extracted from "docker compose config", which only happens when Deployed with Komodo. Can you try a single Re/deploy with Komodo, and see if this fixes this issue?
yes, after redeploying, it is showing as running! I'm fine with you closing this.
<!-- gh-comment-id:3242514097 -->
@LunkSnee commented on GitHub (Sep 1, 2025):
yes, after redeploying, it is showing as running! I'm fine with you closing this.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @LunkSnee on GitHub (Aug 31, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/790
I have a set of stacks that all use the same compose.yaml template file, but with unique project variables. I've pulled this into komodo using "files on server" and it finds the compose and other files to show under "info", however the status stays as "down". Could the monitoring check evaluate the .env variable for the stack?
I set the stack's name in Komodo to "wp-abc" or whatever the ${PROJ} is for that stack.
See my compose file below.
and the .env includes:
@mbecker20 commented on GitHub (Sep 1, 2025):
Komodo should handle this edge case, but this case requires container name to be extracted from "docker compose config", which only happens when Deployed with Komodo. Can you try a single Re/deploy with Komodo, and see if this fixes this issue?
@LunkSnee commented on GitHub (Sep 1, 2025):
yes, after redeploying, it is showing as running! I'm fine with you closing this.