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
When setting up a VM Host with Hetzner, we manually enter the IP address and Hetzner server ID. The https://robot.hetzner.com/doc/webservice/en.html#get-server endpoint of the Hetzner webservice provides a list of all servers, allowing us to find the Hetzner identifier using the IP address.
The text was updated successfully, but these errors were encountered:
Hey, I've a few doubts. Firstly, after running docker exec -it ubicloud-app ./demo/cloudify_server command, IP address and Select provider and location [default: 1] will be asked. Instead of being prompted for the second detail, should all the information be fetched with just the IP address being entered via the API?
Also, the server ID isn't being asked when the docker exec -it ubicloud-app ./demo/cloudify_server command is entered. Please let me know if I am missing something!
Hey, I've a few doubts. Firstly, after running docker exec -it ubicloud-app ./demo/cloudify_server command, IP address and Select provider and location [default: 1] will be asked. Instead of being prompted for the second detail, should all the information be fetched with just the IP address being entered via the API?
Hetzner locations and Ubicloud locations don't match 1-1 all the time and we may want some flexibility there, so I think letting location prompt be as is would be fine.
Also, the server ID isn't being asked when the docker exec -it ubicloud-app ./demo/cloudify_server command is entered. Please let me know if I am missing something!
When setting up a VM Host with Hetzner, we manually enter the IP address and Hetzner server ID. The https://robot.hetzner.com/doc/webservice/en.html#get-server endpoint of the Hetzner webservice provides a list of all servers, allowing us to find the Hetzner identifier using the IP address.
The text was updated successfully, but these errors were encountered: