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 -stage file allows customizing the worker count with EDA_DEFAULT_WORKERS but the development docker-compose does not
Sugested feature result
I realize there may be platform differences (like running on a Mac) that may prevent replicas: from working correctly in every way that someone wants to use it. And for the -dev target, yeah, it makes sense to make it as flexible as possible. However, I would argue that if this should be the run-anywhere target, then it makes more sense to use 1 worker. So I'd suggest the result would be either:
the docker-compose-dev option is configurable with the env var EDA_DEFAULT_WORKERS
the docker-compose-dev option just runs 1 worker
Additional information
No response
The text was updated successfully, but these errors were encountered:
Please confirm the following
Feature type
New Feature
Feature Summary
Ability to use this docker-compose file with only 1 task & podman node
https://github.com/ansible/eda-server/blob/main/tools/docker/docker-compose-dev.yaml
Steps to reproduce
Run the docker-compose development environment.
Compare to others like docker-compose-stage.yaml
Current results
The -stage file allows customizing the worker count with
EDA_DEFAULT_WORKERS
but the development docker-compose does notSugested feature result
I realize there may be platform differences (like running on a Mac) that may prevent
replicas:
from working correctly in every way that someone wants to use it. And for the -dev target, yeah, it makes sense to make it as flexible as possible. However, I would argue that if this should be the run-anywhere target, then it makes more sense to use 1 worker. So I'd suggest the result would be either:EDA_DEFAULT_WORKERS
Additional information
No response
The text was updated successfully, but these errors were encountered: