Open lincoln017 opened 2 weeks ago
Hi @lincoln017
Thanks for evaluating Azimutt.
The explore
command is launching the Gateway and opens Azimutt with the provided url, so it should work.
The message about starting the gateway is a suggestion when the database is not reachable but it may be something else.
Can you show me some screenshots? Or we can plan a call if you prefer, reach out to contact@azimutt.app.
Let me know.
This is the full command of the export that works perfectly: npx azimutt@latest export postgresql://myuser:mypassword@localhost:5432/mydb --schema public
When I enter this: npx azimutt@latest explore postgresql://myuser:mypassword@localhost:5432/mydb
I get the following from the command line:
{"level":30,"time":1731188909908,"pid":95419,"hostname":"myhost","msg":"Server listening at http://[::1]:4177"} {"level":30,"time":1731188909909,"pid":95419,"hostname":"myhost","msg":"Server listening at http://127.0.0.1:4177"} opening https://azimutt.app/create#postgresql%3A%2F%2Fmyuser%3Amypassword%40localhost%3A5432%2Fmydb
... and a browser window opens with a title of "Creating project" and a pop dialog that reads Azimutt gateway: Internal Server Error: , forgot to start the local gateway? (npx azimutt@latest gateway)
Looking to evaluate the product, so apologies for what is likely a basic question...
When I enter "npx azimutt@latest export", I get a .json file as expected and everything works fine.
When I enter "npx azimutt@latest explore", I get a message saying I forgot to start the gateway. But if I launch the gateway in a separate window via "npx aziumtt@latest gateway" and then reissue the explore command, I get the same error message.
What am I missing here?