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
{{ message }}
This repository has been archived by the owner on Jan 20, 2021. It is now read-only.
Right now the UI is developed towards a single CloudStack Management Server as it assume the API will be available under /client/api
This is set in config.json:
"apiBase": "/client/api"
This hard-codes the API to be available on /client/api while using reverse proxies multiple APIs could be made available:
/api/manager1
/api/manager2
/api/manager3
In the JSON we could have support for different servers:
"servers": [
{
"name": "Manager 1",
"apiBase": "/api/manager1"
},
{
"name": "Manager 2",
"apiBase": "/api/manager2"
},
{
"name": "Manager 3",
"apiBase": "/api/manager3"
}
]
On the login page a dropdown menu could be shown when multiple servers are defined in the JSON file so that users can select the different server they want to log in to.
The text was updated successfully, but these errors were encountered:
Understood. This support is for different CloudStack installations. In our use-case we have CloudStack installations in Amsterdam, Miami and Barcelona and even multiple installations in Amsterdam.
With this support we can have one deployment of the UI under one URL where we can point customers to.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now the UI is developed towards a single CloudStack Management Server as it assume the API will be available under /client/api
This is set in config.json:
This hard-codes the API to be available on /client/api while using reverse proxies multiple APIs could be made available:
In the JSON we could have support for different servers:
The text was updated successfully, but these errors were encountered: