googoloid

I think for me, either would work but in different contexts: - as an npm package for convenience for a node project, so i can just add an npm script to launch it on a local db - for more general personal use, a flatpak-distributed app would be preferred (installing npm packages globally is a hassle)

I would want the source to be open for either case though (like others have mentioned too).

Ok so it does work as I understood originally.

If the CLI allows your domain to connect to it and do arbitrary DB queries, it's definitely not something I could trust. Even if I knew you to be perfectly respectable, your hosting could get hacked and then there would be a pipeline for an attacker to my DB.

It's a reasonable way to do some things, but I definitely feel this cannot be called local-first, since it explicitly allows and expects external domains to connect to it.

The bundle size is no issue whatsoever for a cli tool for devs, it's only really a problem when serving via the internet.

So this uses the local cli tool to allow your hosted code to connect to the db? Sounds a bit sketchy to me

Well, I'll be happy enough with an rpm on fedora!

This looks pretty exciting, the documentation aspect of api-client-in-md has potential!

When do you think you'll have a linux client available? I'm hoping it will be available via flatpak :)