Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build a Docker Compose version #2

Open
4 of 5 tasks
samdbmg opened this issue Jan 7, 2023 · 1 comment
Open
4 of 5 tasks

Build a Docker Compose version #2

samdbmg opened this issue Jan 7, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@samdbmg
Copy link
Owner

samdbmg commented Jan 7, 2023

It would be nice to have a single Compose file that has the same effect as deploying this role. So it generates a suitable Traefik config, and runs the socket proxy, forward auth and Traefik containers, configured by some env vars. That way the non-Ansible user experience becomes "copy the compose file, set config vars, do docker-compose up

  • Figure out config file generation
  • Build the Compose file and get it working
  • Look at better ways of keeping config options in sync between env vars and Ansible vars?
  • Adapt the CI to run the same set of tests in Compose mode
  • Document this new way of working
@samdbmg samdbmg added the enhancement New feature or request label Jan 7, 2023
@samdbmg
Copy link
Owner Author

samdbmg commented Jan 7, 2023

Progress so far in https://github.com/samdbmg/ansible-traefik-auth-proxy/tree/feat/docker-version

Config File Sync
For keeping the config files in sync, it might be possible to parse defaults/main.yml to extract all the config keys, then set them programmatically using set_fact?

Or get the entire list and write an entrypoint script that sets anything starting PROXY_ as an extravar - maybe that's neater.

Compose File
It might make more sense in the docs to recommend doing docker-compose run config-generator and then docker-compose up -d reverse-proxy to avoid having to generate config every time, and oddities where startup fails until the config is available.

samdbmg added a commit that referenced this issue Jan 7, 2023
Switches docker-only mode to generate the config file first, and then
start up in a separate second step, to avoid oddities where config
generation takes a while.

Refs #2
samdbmg added a commit that referenced this issue Jan 8, 2023
Switches docker-only mode to generate the config file first, and then
start up in a separate second step, to avoid oddities where config
generation takes a while.

Refs #2
samdbmg added a commit that referenced this issue Jan 8, 2023
Switches docker-only mode to generate the config file first, and then
start up in a separate second step, to avoid oddities where config
generation takes a while.

Refs #2
samdbmg added a commit that referenced this issue Jan 8, 2023
Switches docker-only mode to generate the config file first, and then
start up in a separate second step, to avoid oddities where config
generation takes a while.

Refs #2
samdbmg added a commit that referenced this issue Jan 22, 2023
Switches docker-only mode to generate the config file first, and then
start up in a separate second step, to avoid oddities where config
generation takes a while.

Refs #2
samdbmg added a commit that referenced this issue Jan 23, 2023
Switches docker-only mode to generate the config file first, and then
start up in a separate second step, to avoid oddities where config
generation takes a while.

Refs #2
samdbmg added a commit that referenced this issue Jan 24, 2023
Switches docker-only mode to generate the config file first, and then
start up in a separate second step, to avoid oddities where config
generation takes a while.

Refs #2
samdbmg added a commit that referenced this issue Nov 5, 2023
Switches docker-only mode to generate the config file first, and then
start up in a separate second step, to avoid oddities where config
generation takes a while.

Refs #2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant