Maybe we move #3 to compose-stacks/traefik and close this?
Traefik "stack": https://git.autonomic.zone/compose-stacks/traefik
traefik.autonomic.zone config: https://git.autonomic.zone/autonomic-cooperative/coop-cloud-apps/src/branch/main/traefik.autonomic.zone.env
Maybe we move #3 to `compose-stacks/traefik` and close this?
If we do this we can sunset all the *.autonomic.zone repositories and move to this compose-stacks config /coop-cloud-apps env situation. That would make it easier to focus on a single config and keep it up-to-date.
With the caveat that we'll have to take care of manual deployments for a bit if we do this, I'm well up for moving to the monorepo setup. Do we want to maybe have a plan for keeping our CD going? I might have a poke around now...
If we do this we can sunset all the `*.autonomic.zone` repositories and move to this compose-stacks config /coop-cloud-apps env situation. That would make it easier to focus on a single config and keep it up-to-date.
With the caveat that we'll have to take care of manual deployments for a bit if we do this, I'm well up for moving to the monorepo setup. Do we want to maybe have a plan for keeping our CD going? I might have a poke around now...
Traefik "stack": https://git.autonomic.zone/compose-stacks/traefik
traefik.autonomic.zone config: https://git.autonomic.zone/autonomic-cooperative/coop-cloud-apps/src/branch/main/traefik.autonomic.zone.env
Maybe we move #3 to
compose-stacks/traefikand close this?If we do this we can sunset all the
*.autonomic.zonerepositories and move to this compose-stacks config /coop-cloud-apps env situation. That would make it easier to focus on a single config and keep it up-to-date.With the caveat that we'll have to take care of manual deployments for a bit if we do this, I'm well up for moving to the monorepo setup. Do we want to maybe have a plan for keeping our CD going? I might have a poke around now...
Since this is wider than this repo, let's keep the ball rolling on compose-stacks/planning#18.