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

Use envsubst to allow frontend to find backend with env vars #1060

Merged
merged 5 commits into from
Jul 24, 2024

Conversation

flavour
Copy link
Contributor

@flavour flavour commented Jul 23, 2024

docker compose is a great simple orchestration system, but for production purposes we need to support others, for which the hardcoding of backend:port in the frontend nginx.conf is far from ideal...we can use modern nginx docker ability to use envsubst to achieve this instead, which allows full control via ENV vars

Changes

How I tested this

Used a custom ui-frontend which I built from this script...other dockers were identical.

Notes

Checklist

  • PR has an informative and human-readable title (this will be pulled into the release notes)
  • Changes are limited to a single goal (no scope creep)
  • Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
  • Any change in functionality is tested
  • [N/A] New functions are documented (with a description, list of inputs, and expected output)
  • [N/A] Placeholder code is flagged / future TODOs are captured in comments
  • [N/A] Project documentation has been updated if adding/changing functionality.

flavour and others added 3 commits July 23, 2024 18:49
This structure more naturally fits what docker expects.
A docker-compose file at the root, with docker files
for the respective services in those modules.

I have tested this locally for the prod build
and pushed things and I believe it works for
the other cases too.

TODO:
 - dockerx build instructions
 - automating the build & versioning of images with new releases
…e forwarding docker-compose to docker compose
@skrawcz skrawcz changed the base branch from main to reorganize_docker July 24, 2024 05:07
This structure more naturally fits what docker expects.
A docker-compose file at the root, with docker files
for the respective services in those modules.

I have tested this locally for the prod build
and pushed things and I believe it works for
the other cases too.

TODO:
 - dockerx build instructions
 - automating the build & versioning of images with new releases
@skrawcz skrawcz changed the base branch from reorganize_docker to main July 24, 2024 05:32
@skrawcz skrawcz merged commit 05a775a into DAGWorks-Inc:main Jul 24, 2024
25 checks passed
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

Successfully merging this pull request may close these issues.

2 participants