Skip to content
New issue

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

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

Already on GitHub? # to your account

Docs: add guide for exposing clickhouse #5

Open
4 tasks
MykalMachon opened this issue Nov 26, 2023 · 2 comments
Open
4 tasks

Docs: add guide for exposing clickhouse #5

MykalMachon opened this issue Nov 26, 2023 · 2 comments
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers

Comments

@MykalMachon
Copy link
Collaborator

Summary of issue

By default, the ClickHouse service is not exposed over the internet; it's only available on the Railway internal/private network. However, by using Railway's TCP Proxying feature you could easily expose the service over the public internet.

While I think the service being private is a good default, it does make sense to include a guide on making the service public using the aforementioned TCP proxying feature.

Specs and requirements

The docs for this should:

  • Be in the README.md for this repo under "Additional Resources"
  • Be formatted as a simple bulleted list with steps to exposing the service
  • Go over what environment variables should be changed as part of exposing ClickHouse publicly
  • Link to railway's docs on both TCP proxying and public/vs private services
@MykalMachon MykalMachon added documentation Improvements or additions to documentation good first issue Good for newcomers labels Nov 26, 2023
@casanea
Copy link

casanea commented Dec 22, 2024

Hey @MykalMachon

I'm looking for the same!
Have you been able to access the data somehow? I'd love to get some help as I'm struggling here 🥲

@MykalMachon
Copy link
Collaborator Author

Hi @casanea,
I've never had a need for external access personally, so I never got around to working on this.

You should be able to expose the service by simply adding a public address and updating the existing variables to point at it.

Feel free to put in a PR if you ever find a way!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants