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

Add docker build workflow #2

Merged
merged 2 commits into from
Jul 17, 2023
Merged

Add docker build workflow #2

merged 2 commits into from
Jul 17, 2023

Conversation

frankh
Copy link
Contributor

@frankh frankh commented May 25, 2023

  • 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

ch_ca = os.getenv("CLICKHOUSE_CA", None)
ch_secure = os.getenv("CLICKHOUSE_SECURE", True)
ch_secure = os.getenv("CLICKHOUSE_SECURE", "true") == "true"
Copy link
Contributor

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

@yakkomajuri
Copy link
Contributor

was def on my list to publish an image for this, thanks!

@frankh frankh marked this pull request as ready for review May 25, 2023 14:08
@frankh frankh requested a review from yakkomajuri May 25, 2023 14:08
@yakkomajuri
Copy link
Contributor

yakkomajuri commented May 26, 2023

can't do npm run start in prod - the dev build is not optimized well but worse is that it will just show React "screens of death" to the user. we should rather figure out a proper server then. what do you mean with serve not supporting proxying though?

@mstump
Copy link

mstump commented Jun 22, 2023

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:

mstump@100d585

@frankh frankh force-pushed the frank/chart branch 2 times, most recently from 288ff1f to edc681b Compare July 17, 2023 08:30
@frankh frankh merged commit e5197ca into main Jul 17, 2023
2 checks passed
- "3000:3000"
=======
network_mode: "service:web"
>>>>>>> 0921a8c (Add helm chart)

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....

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.

4 participants