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

NOT AN ISSUE! is it possible to split the services on two servers? (one server for HTTPS and another for DNS) #361

Open
okorsky opened this issue Sep 4, 2024 · 1 comment

Comments

@okorsky
Copy link

okorsky commented Sep 4, 2024

This is not an issue, it's more like a feature question.

is it possible to split the DNS and HTTPS services on two servers? where both will point to the same DB?

Is there a recommended configuration for that setup?

I'm thinking that if I setup 2 servers pointing to the same PostgreSQL database then it should work. But not sure if that's the case.

@okorsky okorsky changed the title Is it possible to split the services on two servers? (one server for HTTPS and another for DNS) NOT AN ISSUE! is it possible to split the services on two servers? (one server for HTTPS and another for DNS) Sep 4, 2024
@maddes-b
Copy link

Having API and DNS on two different machines is not intended, you may try with sharing the DB file from the API machine (does DB updates: /register and /update) to the DNS machine (read only).

Otherwise if the API and DNS are on the same machine, you can serve the API under a different domain by binding API to a local IP (127.0.0.1, ::1, or similar) and use a reverse proxy (e.g. nginx) to accept requests and forward to the API's IP and port.
See #363 for related information.

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

2 participants