Yup. This is just a straightforward client. Unfamiliar with dbgate but just looked at the docs. It’s also just a client as well. Unsure what other backend service you may have been referring to.
It seems there is a misunderstanding. To be clear, this is what I mean:
┌───────────────────────┐
│ Browser │
└───────────────────────┘
▲
│ port 443 open
│
│
┌────┼──────────────────┐
│ Proxy (traefik) │
└───────────────────────┘
▲
│
│ web port open to proxy
│
│
┌────┼──────────────────┐
│ DBgate (in docker) │
└───────────────────────┘
▲
│
│
│
┌────┼──────────────────┐
│ Database │
└───────────────────────┘
This way DBgate serves the web app to the browser, but also acts as a ‘backend’ which connects to the database. This way my databases are not exposed to the web, only the proxy is, which handles domain name routing and http traffic.
Are you sure? Because thats how dbgate works, and I thought this was similar.
Yup. This is just a straightforward client. Unfamiliar with dbgate but just looked at the docs. It’s also just a client as well. Unsure what other backend service you may have been referring to.
It seems there is a misunderstanding. To be clear, this is what I mean:
┌───────────────────────┐ │ Browser │ └───────────────────────┘ ▲ │ port 443 open │ │ ┌────┼──────────────────┐ │ Proxy (traefik) │ └───────────────────────┘ ▲ │ │ web port open to proxy │ │ ┌────┼──────────────────┐ │ DBgate (in docker) │ └───────────────────────┘ ▲ │ │ │ ┌────┼──────────────────┐ │ Database │ └───────────────────────┘This way DBgate serves the web app to the browser, but also acts as a ‘backend’ which connects to the database. This way my databases are not exposed to the web, only the proxy is, which handles domain name routing and http traffic.