175
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 08 Apr 2025
175 points (98.9% liked)
Selfhosted
58936 readers
30 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
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.
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: https://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 🤣🤣🤣
https://github.com/dbgate/dbgate/tree/master/plugins/dbgate-plugin-postgres
Yet you ignore I pointed to the api component in the repo...
What the hell are you talking about? Just look at the Dockerfile.
You think that line isn't running a server?
Thr repo makes it very obvious that it runs a server that the webgui connects to. Its fine if you dont know shit but dont be a dick while being stupid.