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.
I…don’t think I need to.
You dont need to indeed, but since you mentioned them first.
If you’re unfamiliar with all of this, that’s your job to get educated.
I’m a software engineer from way before the js hype, so I think I’m properly educated thanks.
The “proof” is right there in all it’s glory for you to peruse.
Indeed, here is the api part: github.com/dbgate/dbgate/tree/master/…/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.
Markaos@discuss.tchncs.de 1 year 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 year 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 year 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.
🤣
Markaos@discuss.tchncs.de 1 year ago
Node.js is a web server. It doesn’t run in a browser, therefore doesn’t deal with the browser sandbox. That should answer your first dig.
For the second part, WebRTC is a standard that allows two WebRTC peers to communicate. You can’t use WebRTC to open an arbitrary TCP or UDP stream to for example a database, unless said database decides to implement a WebRTC peer support.
just_another_person@lemmy.world 1 year ago
Friend, I’ve literally linked the DBGate repo. You can see yourself there is no server component running, and it’s all in browser. It’s literally called “web-based”. Have a look here: docs.dbgate.io/web-app-config/
So in your world, you imagine that if you run this project, there is a server running…somewhere, and then it’s forwarding all requests from the browser to this server, and the server is making the connections to the DB endpoint? Lolzzzz 🤣🤣🤣
github.com/dbgate/…/dbgate-plugin-postgres