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
Is there a switch option for horizon-container start to run with the default index of 1 but some other file e.g. anax.conf in my current directory ? I am able to run with horizon-container start 1 anax.conf. Instead, is this possible horizon-container start --default-file anax.conf?
Once the container has started successfully, is there a command on the Hub side to check end-to-end connectivity?
Running this command sudo installer -pkg "horizon-cli-2.24.18.pkg" -target / results in these messages for me.
installer: Package name is horizon-cli-2.24.18
installer: Installing at base path /
installer: The install was successful.
Whereas, the documentation reports messages related to upgradation.
installer: Package name is horizon-cli-2.24.18
installer: Upgrading at base path /
installer: The upgrade was successful.
When does the installer command respond with messages on upgradation?
The text was updated successfully, but these errors were encountered:
If HZN_DEVICE_NODE is not added in /etc/default/horizon, then what value is used? This configuration variable seems to be needed when installing agent on Ubuntu.
horizon-cli
package before these commands?wget http://pkg.bluehorizon.network/macos/horizon-cli-2.24.18.pkg sudo installer -pkg "horizon-cli-2.24.18.pkg" -target /
Is there a switch option for
horizon-container start
to run with the default index of 1 but some other file e.g.anax.conf
in my current directory ? I am able to run withhorizon-container start 1 anax.conf
. Instead, is this possiblehorizon-container start --default-file anax.conf
?Once the container has started successfully, is there a command on the Hub side to check end-to-end connectivity?
Running this command
sudo installer -pkg "horizon-cli-2.24.18.pkg" -target /
results in these messages for me.Whereas, the documentation reports messages related to upgradation.
When does the
installer
command respond with messages on upgradation?The text was updated successfully, but these errors were encountered: