-
Notifications
You must be signed in to change notification settings - Fork 35
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
Add docker build workflow #2
Conversation
frankh
commented
May 25, 2023
•
edited
Loading
edited
- add github actions to build containers
- create a helm chart for deploying
- proxy api via frontend so we can have a single entrypoint (simplifies deployment a lot)
- use npm run start instead of serve (serve doesn't support proxying :()
- should fix this to use a proper server at some point
housewatch/clickhouse/client.py
Outdated
ch_ca = os.getenv("CLICKHOUSE_CA", None) | ||
ch_secure = os.getenv("CLICKHOUSE_SECURE", True) | ||
ch_secure = os.getenv("CLICKHOUSE_SECURE", "true") == "true" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this won't work because we want to default to true, yet docker will give us an empty string here
was def on my list to publish an image for this, thanks! |
can't do |
I spent a little bit of time today and yesterday getting arm64 containers built and resolving the issues raised. I want to confirm I'm on the right path towards getting this PR merged: |
288ff1f
to
edc681b
Compare
- "3000:3000" | ||
======= | ||
network_mode: "service:web" | ||
>>>>>>> 0921a8c (Add helm chart) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just FYI, it looks like a set of merge conflict markers was checked in here....