You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Hi, I am starting out with Immudb and able to run it both with Docker and also using the binary download. So far so good. Running with Docker, I see that the web console is enabled, but with the OSX binary I get the message saying that it was not built with the embedded web console.
Trying to access 0.0.0.0:8080 running with the Docker immudb and I get a "connection refused" error. Checking the environment and I see that 0.0.0.0:8080 has not been bound to anything internally?
Then, doing a naive download/npm install of this repo and it fails with many libsass and node-gyp errors.
Is there any recent documentation on how to properly get the Immudb web console running?
TIA,
Steve
The text was updated successfully, but these errors were encountered:
Thanks for reporting it @stevexm.
I was able to reproduce the issue installing immudb with brew brew install immudb, we'll update the formulae asap.
However, using the binary from the release was working as expected, as well with running immudb in docker as described here https://docs.immudb.io/master/getstarted/quickstart.html
Describe the bug
Hi, I am starting out with Immudb and able to run it both with Docker and also using the binary download. So far so good. Running with Docker, I see that the web console is enabled, but with the OSX binary I get the message saying that it was not built with the embedded web console.
Trying to access 0.0.0.0:8080 running with the Docker immudb and I get a "connection refused" error. Checking the environment and I see that 0.0.0.0:8080 has not been bound to anything internally?
Then, doing a naive download/npm install of this repo and it fails with many libsass and node-gyp errors.
Is there any recent documentation on how to properly get the Immudb web console running?
TIA,
Steve
The text was updated successfully, but these errors were encountered: