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 443open
│
│
┌────┼──────────────────┐
│ 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.
That’s not how it works, or maybe the arrows are pointing the wrong direction in your ASCII. DBgate is an in-browser application in the same way that the other posted is, just with different features. They both run completely in the browser, BUT the files need to get loaded there first right? So the docker version of DBgate is simply starting a tiny web server that bootstraps the client application into your browser when you visit the local port. It’s right in their docs.
No server-side code at all, and in fact, you can kill the docker container after you get it loaded in your browser if you want to double check 😉
Huh? This is a database client. There is no backend. You point it to a database, and it connects to the database. That’s all it does.
I’m not sure what other backend you may be referring to, but it will use whatever network your desktop is using for comms.
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.
That’s not how it works, or maybe the arrows are pointing the wrong direction in your ASCII. DBgate is an in-browser application in the same way that the other posted is, just with different features. They both run completely in the browser, BUT the files need to get loaded there first right? So the docker version of DBgate is simply starting a tiny web server that bootstraps the client application into your browser when you visit the local port. It’s right in their docs.
No server-side code at all, and in fact, you can kill the docker container after you get it loaded in your browser if you want to double check 😉