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

hxldash-docker docker-compose.yml MVP of a more complete stack #5

Open
fititnt opened this issue Apr 5, 2020 · 1 comment
Open

Comments

@fititnt
Copy link
Member

fititnt commented Apr 5, 2020

Instead of just create a single docker-compose.yml file, this issue is about create two. One should focus on the issue #3 (local development, maybe not even the #2 PostgreSQL). The other one, more complete, is what this issue is about: at bare minimum should include a reverse proxy with HTTPS termination in addition to the hxldash. All other non-essential containers should be added to this docker compose file.

If the user need something that may not need to run the simplest docker for local development, it should be on this file, not on the #3.

Note: this issue may not be finished at all, but still be used to reference other issues that are not really need for local development. This docker-compose file also will try focus on software and configuration that could be used in production with some more changes and fine tuning.

@fititnt
Copy link
Member Author

fititnt commented Apr 5, 2020

Not just because of semantic issue (repository called 'hxldash-docker' containing more than just hxldash) but because just to setup an Traefik proxy in a decent way would be better done some configuration outside docker (I normally would with Ansible or just document what shell commands where executed) I will move this issue for a complete different repository.

The draft is at https://github.com/covid-taskforce-cplp/hxl-standard-tools-stack.

Other issues that may be impacted by this change:

  • Add hxl-proxy on the stack Add hxl-proxy on the stack #4: this and other tools definely should go on a more generic repository (now that have an draft for this) and not here.
  • MVP of PostgreSQL on hxldash-docker docker-compose.yml MVP of PostgreSQL on hxldash-docker docker-compose.yml #2: if is possible to run hxldash just with sqlite, makes sense to also move this issue to the other repository.
  • (generic impact): the hxldash-docker repository actually tend to move some of its complexity (maybe even not have an docker-compose.yml file) to the other repository. One very notable change is that now we're very likely to have to pre-build this image and share public than make users to create all the time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant