Closed G2Jose closed 2 hours ago
Explained by https://github.com/instantdb/instant/issues/168
I had DEV=true
set in my environment. This was causing instant-cli
to try to connect to a local instance of InstantDB instead of the cloud. Removing this fixes the issue.
I'd suggest instant-cli
should take an explicit argument to connect to local vs cloud instances, as opposed to a rather generic environment variable.
Great idea guys!
i.m.o:
DEV
to something like INSTANT_CLI_DEV
INSTANT_CLI_API_URI
env apiURI
, which, does the following:
a. if INSTANT_CLI_API_URI is set, we use that
b. if INSTANT_CLI_DEV is set, we use localhost
c. else we use instantdb.com We'll get to this, but if you guys want to pop in a PR for it, feel free!
cc @markyfyi if you think differently
Added INSTANT_CLI_API_URI
and INSTANT_CLI_DEV
in v0.13.0! @G2Jose PTAL and let us know if you need anything else! cc @stopachka
Added
INSTANT_CLI_API_URI
andINSTANT_CLI_DEV
in v0.13.0! @G2Jose PTAL and let us know if you need anything else! cc @stopachka
That was so quick, thank you!
I can't seem to login via instant-cli using the command
yarn instant-cli login
(also tried the same withnpx
).Here's the error I'm seeing:
Things I've tried:
npx
andyarn
Versions: