In general sometimes a vars from some service has no the same meaning in different playgroups:
in ala-hub: bie.baseUrl=https://csic.gbif.es/especies are generated bie.baseUrl=https://csic.gbif.es incorrectly but in bie-hub should be: bie.baseURL=https://csic.gbif.es
In bie-hub template: serverURL: {{ bie_base_url }}{{bie_hub_context_path}}
spatial url base in ala-hub looks incorrect (has /ws)
This happens when some service with a different userdetails_base_url (like dashboard) is installed together with CAS.
biocache_base_url is different in dashboards from the rest
userdetails_base_url is different in ala-hub and biocache-service vs CAS.
Solution, to use an additional different name for each uses.
In general sometimes a vars from some service has no the same meaning in different playgroups:
bie.baseUrl=https://csic.gbif.es/especiesare generatedbie.baseUrl=https://csic.gbif.esincorrectly but in bie-hub should be:bie.baseURL=https://csic.gbif.esInbie-hubtemplate:serverURL: {{ bie_base_url }}{{bie_hub_context_path}}userdetailsvar incaspointing to: https://auth-es.l-a.site/userdetails/userdetails/registration/createAccount instead of: https://auth-es.l-a.site/userdetails/registration/createAccountuserdetails_base_url(like dashboard) is installed together with CAS.biocache_base_urlis different in dashboards from the restuserdetails_base_urlis different in ala-hub and biocache-service vs CAS.Solution, to use an additional different name for each uses.
We should add this to the tests.