DbGate is connecting to my postgresql db. If I kill the container the communication is cut off. The ports 3000, 8089, 5001, 5432 are not open. How does DbGate load my postgres data then, if no backend? Sometimes I use it when my client messes up something thats only repairable in the db. Thats the exact scenario where its useful to run it in docker.
It’s right in their docs
Where? The app runs in the browser, but the data is still remote (from the pov of the browser)
DBGate is an application running in your browser. Just like any other desktop application, except it’s code is executed in the browser, and not a standalone window. DBGate uses the runtime platform of your browser to execute code and create connections to the database you’re using. That’s where you’re getting confused. There is nothing running in the docker container except a dumb HTTP server that allows your browser to load the code to executed, just as if you had visited their website.
This same exact code can also be packaged to run in Electron as a standalone window in your desktop so it seems like its own app. Same exact code that runs in your browser, but using Electron to host and execute its code.
If you’re unfamiliar with all of this, that’s your job to get educated. This is how browser-based JS software works. The “proof” is right there in all it’s glory for you to peruse.
The point is: DBgate is capable of running in a container which makes a connection to a database. You insist this is not how it works, but yet its the way I have set it up.
My question was if outerbase is usable in the same way. You clearly have not enough knowledge to answer that, so no, my question isnt answered.
Ok, I updated my drawing, so the arrows are correct:
┌─────────────────────────────────────────────────────────────────┐ │ Browser │ └─────────────────────────────────────────────────────────────────┘ ▲ │ :443 │ :80 ▼ ┌────────────────────────────────────────────────────────────────┐ │ Proxy (traefik) │ └────────────────────────────────────────────────────────────────┘ ▲ ▲ ▲ │ │ │ │ :3000 │ :8085 │ :5001 │ │ │ ▼ ▼ ▼ ┌───────────────────────┐ ┌────────────────┐ ┌────────────────┐ │ DBgate (in docker) │ │ pgBackupWeb │ │ My custom app │ └───────────────────────┘ └────────────────┘ └────────────────┘ ▲ ▲ ▲ │ :5432 │ :5432 │ :5432 │ │ │ ▼ ▼ ▼ ┌────────────────────────────────────────────────────────────────┐ │ Database │ └────────────────────────────────────────────────────────────────┘DbGate is connecting to my postgresql db. If I kill the container the communication is cut off. The ports 3000, 8089, 5001, 5432 are not open. How does DbGate load my postgres data then, if no backend? Sometimes I use it when my client messes up something thats only repairable in the db. Thats the exact scenario where its useful to run it in docker.
Where? The app runs in the browser, but the data is still remote (from the pov of the browser)
Again, no.
DBGate is an application running in your browser. Just like any other desktop application, except it’s code is executed in the browser, and not a standalone window. DBGate uses the runtime platform of your browser to execute code and create connections to the database you’re using. That’s where you’re getting confused. There is nothing running in the docker container except a dumb HTTP server that allows your browser to load the code to executed, just as if you had visited their website.
This same exact code can also be packaged to run in Electron as a standalone window in your desktop so it seems like its own app. Same exact code that runs in your browser, but using Electron to host and execute its code.
Show me the docs. It really sounds like you’re confidentially incorrect :-)
The app part is indeed just running in the browser. But it needs the data over an external connection. Explain how it can read/write the data to me.
I…don’t think I need to. It’s all open source. Here is the DBGate repo right here.
If you’re unfamiliar with all of this, that’s your job to get educated. This is how browser-based JS software works. The “proof” is right there in all it’s glory for you to peruse.
You dont need to indeed, but since you mentioned them first.
I’m a software engineer from way before the js hype, so I think I’m properly educated thanks.
Indeed, here is the api part: https://github.com/dbgate/dbgate/tree/master/packages/api
That is a LOCAL running interface. It’s not something being run as a server-side interface in the docker container.
I’m not sure what point you’re trying to make, but at this point, you’re original concern and question has been answered.
The point is: DBgate is capable of running in a container which makes a connection to a database. You insist this is not how it works, but yet its the way I have set it up.
My question was if outerbase is usable in the same way. You clearly have not enough knowledge to answer that, so no, my question isnt answered.