Selfhosted

46127 readers

680 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.

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

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

187

GitHub - outerbase/studio: A lightweight Database GUI in your browser. It supports connecting to Postgres, MySQL, and SQLite. (github.com)

submitted 1 week ago by jogai_san@lemmy.world to c/selfhosted@lemmy.world

42 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] jogai_san@lemmy.world 1 points 1 week ago (1 children)

Are you sure? Because thats how dbgate works, and I thought this was similar.

[–] just_another_person@lemmy.world 1 points 1 week ago (1 children)

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.

[–] jogai_san@lemmy.world 1 points 1 week ago* (last edited 1 week ago) (1 children)

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.

[–] just_another_person@lemmy.world 1 points 1 week ago

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 😉