Conversation
pablothedude
force-pushed
the
bugfix/fix-initial-initialisation
branch
from
4d80f6c to
b989625
Compare
|
|
||
| echo -e "docker compose --profile php -f docker-compose.yml "${docker_compose_args[@]}" "${extra_compose_args}" up -d "${@:$number_of_dev_envs}"\n" | ||
| docker compose --profile php -f docker-compose.yml ${docker_compose_args[@]} ${extra_compose_args} up -d "${@:$number_of_dev_envs}" | ||
| echo -e "docker compose --profile oidc -f docker-compose.yml "${docker_compose_args[@]}" "${extra_compose_args}" up -d "${@:$number_of_dev_envs}"\n" |
There was a problem hiding this comment.
@quartje is it possible to do this in order to be able to push from Manage to EB and don't get an exception in Manage?
Or is this the wrong way to achieve this?
And should I for example add php to the docker-compose services that already have oidc as proffile? Becuase I don't fully understand why I need oidc in order to push from Manage to Engine.
There was a problem hiding this comment.
Manage pushes to both oidc and eb. This would fix that issue.
In an ideal world, Manage would be configured dynamically (so --profile php would config manage only to push to eb, not to oidc).
|
|
||
| echo -e "docker compose --profile php -f docker-compose.yml "${docker_compose_args[@]}" "${extra_compose_args}" up -d "${@:$number_of_dev_envs}"\n" | ||
| docker compose --profile php -f docker-compose.yml ${docker_compose_args[@]} ${extra_compose_args} up -d "${@:$number_of_dev_envs}" | ||
| echo -e "docker compose --profile oidc -f docker-compose.yml "${docker_compose_args[@]}" "${extra_compose_args}" up -d "${@:$number_of_dev_envs}"\n" |
There was a problem hiding this comment.
Manage pushes to both oidc and eb. This would fix that issue.
In an ideal world, Manage would be configured dynamically (so --profile php would config manage only to push to eb, not to oidc).
2 participants
No description provided.