I’m using it since before v0.10, never had issues. But I’m not using everything. But container management, auto-update, and proxy never gave me a problem.

The perfect vector for a nefarious experiment…

Research what different routes there are to take. Pick one you like. Try to set it up without depending on it just yet. Learn from your mistakes, and what drawbacks you find. Reevaluate your choices and pick another (mabye even on different storage, and do it all again. I bet most selfhosters go trough a few different setups till landing on a favorite. For me, its cosmos-server at home, and a fairly vanilla containeraized treafik setup for my vps.

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

Personally, I use sterlingpdf, but there are others: https://selfh.st/apps/?tag=PDF

Its a hosted tool and everything runs in the browser. It would be interesting to compare results because it could be that c++ is better suited for these kinds of operations.

For me this begs the question, why does this question always come up in selfhosted communities? ;)

For me I like self-hosted apps because I switch between desktop and laptop, and some tools are nice to have on a phone too. This way I pull it in-house, and can use it everywhere. Besides that, there are two other laptops in the house and if I am using those I have the same tools available as well. It its something I need to help the kids with, and they need to use it more often they too can use it regardless of device. Plus its one less thing to install when setting up a new device.

It’s not for work but self 😉 Honest mistake, I don’t know why or how.

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.