[oleksandr_dem]

It uses the CLI to connect to the database. When you start the tool, it creates a server on your localhost (localhost:4466), and acts as:

- Local database: it stores some stuff locally, like saved queries or DB configurations

- Query runner: when you run a query in the webapp it will call your localhost server, which will connect to the database and execute the SQL statement

It is technically possible to host it elsewhere, but I wouldn't recommend it (there is no documentation).

[googoloid]

Your instructions say to go to https://app.dataramen.xyz/, which definitely isn't the locally hosted server. You might want to change that (and disclose if the local server makes data available to websites outside localhost, which the current instructions seem to imply)

[oleksandr_dem]

Yeah, the entire presentation is a mess, I should've worked more on this side.

I see your concern about running it locally and then visiting a remotely hosted webapp. The way it works is that app.dataramen.xyz will call a localhost server (running on your machine, there is no remote code executed) to connect to the database. So all the data stay on your local machine, plus some webapp stuff stored in browser localstorage.

I went for this setup for essentially 2 reasons:

- I didn't want to ship webapp as part of the CLI tool due to the webapp size (it uses React, so the bundle is 800kb or so, while the entire local server code is 45kb).

- In the long term I want the users being able to connect to multiple servers from one webapp. For example you may have a local server running to interact with your local DB, but at the same time you might have configured a remote self hosted server within your company VPN.

It is a weird setup, but you end up doing weird things when you run an app on $0.00 budget