If you change the configuation of the server (amount of RAM, SSD, etc.) the corresponding footprint is not updated.
When looking at devtools, it seems there is a COR issue with the request to the /serverresource :
Blocage d’une requête multiorigines (Cross-Origin Request) : la politique « Same Origin » ne permet pas de consulter la ressource distante située sur https://dev.api.boavizta.org/v1/server/?verbose=true. Raison : l’en-tête CORS « Access-Control-Allow-Origin » est manquant. Code d’état : 500.
I think there is actually two issues here :
one on Cross Origin Request
one on the UI : when the request fails, we should display an error message on the page to inform the user that the footprint displayed does not match the server he has configured. Otherwise one may simply fail to realize there is an error and use an incorrect footprint.
Happens when calculating the impact based on its configuration on the page https://dataviz.boavizta.org/serversimpact
If you change the configuation of the server (amount of RAM, SSD, etc.) the corresponding footprint is not updated.
When looking at devtools, it seems there is a COR issue with the request to the
/serverresource :I think there is actually two issues here :