Can someone remind him? ;)

Oh awesome

Yeah yeah. For some people self hosting is a lot about pirating content :-) Just trying to make lemmy happen…

Not my content, but always interesting. Since the author always uses refs in his links I set this one to lemmy. Hopefully he’ll be posting on lemmy in the near future ;)

Same.

Only thing is, when I run it the postgresql driver is ‘invalid’. But I’m trying with an older version, like this:

docker run --rm -it --name outerbase --network host -h outerbase.local chewcw/outerbase-studio:v0.9.2

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…

Friend, I’ve literally linked the DBGate repo. You can see yourself there is no server component running

Yet you ignore I pointed to the api component in the repo…

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.

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.

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

Well, I assume there is a backend which takes care of securely connecting to the databases. That way I can connect the backend to the internal network where I can connect to the database, and without exposing the database port still use this from the browser.

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 ;)

I know its resolved, but discovered this today: https://github.com/civilblur/mazanoke

I see now

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

Same for me, that’s why I shared it. I don’t know why he’s not merging PR’s because this fork tries to share everything back.