Closed penberg closed 1 year ago
Is my understanding correct that we want to keep iku-turso-cli closed source @penberg ? In that case we probably need to create a homebrew cask.
My preference that iku-turso-cli
will become open source, but let's talk to @glommer about that. In any case, we can't open it up right now because we're not ready to expose the API to public.
Long term, we want this OSS. Short term, we need a very easy and friction-free way to get this in the hands of beta testers. Homebrew seems like the best way: in theory that exposes the API, but in practice nobody knows about its existence anyway.
While we're on it, should this be renamed to turso-cli ?
As long as the repository is private, there's no point in renaming it.
If you want to rename the CLI program name, it should be turso
or tursoctl
.
I think we can close this now.
Let's do a homebrew tap for installing the CLI on mac:
https://publishing-project.rivendellweb.net/creating-and-running-your-own-homebrew-tap/