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
Users probably aren't aware that they have to make sure foxx-cli talks to the endpoint 127.0.0.1:8999 or whatever arangod happens to be set to listen to during the init phase if they want their init scripts to work correctly.
To simplify this, entrypoint.sh should run the following:
foxx server set default tcp://127.0.0.1:$ARANGO_INIT_PORT
before looping over the files in the init scripts directory and then
foxx server remove default
right after the loop.
This is a DX papercut but it seems like a low-hanging fruit as we're already shipping the foxx-cli.
Users probably aren't aware that they have to make sure foxx-cli talks to the endpoint
127.0.0.1:8999
or whatever arangod happens to be set to listen to during the init phase if they want their init scripts to work correctly.To simplify this, entrypoint.sh should run the following:
before looping over the files in the init scripts directory and then
right after the loop.
This is a DX papercut but it seems like a low-hanging fruit as we're already shipping the
foxx-cli
.This means users can run this:
instead of this:
foxx install /myapp /myapp.zip -H tcp://127.0.0.1:$ARANGO_INIT_PORT
(and don't have to dig into the code to figure out
$ARANGO_INIT_PORT
is even a thing)/cc @joerg84 FYI
The text was updated successfully, but these errors were encountered: