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.
jogai_san@lemmy.world 1 week ago
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.
just_another_person@lemmy.world 1 week ago
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.
jogai_san@lemmy.world 1 week ago
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: github.com/dbgate/dbgate/tree/master/…/api
just_another_person@lemmy.world 1 week ago
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.
Markaos@discuss.tchncs.de 1 week ago
The browser version cannot connect to Postgres without a server-side part, for rather obvious reasons - you can’t just make arbitrary network connections from the browser. Electron build is of course different, as that doesn’t have to deal with the browser sandbox.
By the way, here’s a similar issue documented in Outerbase’s repo:
Not gonna lie, telling people how they need to get educated on stuff you don’t understand ticks me off.
jogai_san@lemmy.world 1 week ago
Thanks for backing me up. The fediverse needs to grow because this way it allows for people to be spout nonsense without being corrected by peers.
Btw, had outerbase running trough docker, but could not figure out a way to connect to my own pSql yet…
just_another_person@lemmy.world 1 week ago
I don’t even know where to begin with this 😂
You had better alert the Internet at large and the developers of the apps being discussed here to let them that the very product they build is impossible then.
Oh…wait: reintech.io/…/using-node-js-to-access-remote-data…
A very basic example on how to do the very thing you said is not possible you say? While you’re at it, you better go alert Zoom, Google, Microsoft, and anyone else with a WebRTC app that they aren’t allowed to make connections to other things from the browser. It’s totally against the rules and impossible.
🤣