The perfect vector for a nefarious experiment...

See my response here: https://lemmy.world/post/31091927/17573933

Its not my project, but my reasoning was that the selfhosted version would give you the same features as premium. I didnt look into detail into it tbh.

He claims he was the main contributor, I think, not the author. Fair disctinction imo. I can see the drive to keep something alive if you contributed a lot to a project, especially if you know the codebase well and think its very much feasible in other environments.

Not gonna lie, telling people how they need to get educated on stuff you don’t understand ticks me off.

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

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: https://github.com/dbgate/dbgate/tree/master/packages/api

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.

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.

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)

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.

Deterministic DDL Export - Replaced AI-based export with native SQL generation

Much better. Now it works for my case, which it didn't before.

If anyone got this running in docker for example, I like to hear from you ;)

Only trough the mobile ui. Or at least not trough the default ui on lemmy.world

https://github.com/vladmandic/pigallery ?