-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update CLARITY GeoServer URIs #66
Comments
We plan to move to the new instance so probably it does not worth the effort to secure the old one. |
What is now the correct instance for all layers (hazard + hazard-le input layers)? https://geoserver.myclimateservice.eu/ ? We have to make the changes in the data packages before we set up the synchronisation between DEV and PROD instance of CSIS and also in EMIKAT which currently calls http://services.clarity-h2020.eu:8080 |
Question to @DanielRodera & @maesbri
@therter can prepare the update statements |
The following update statements will adjust the geoserver urls, if only the url base must be changed. update node__field_reference_path set field_reference_path_value = replace(field_reference_path_value, 'https://clarity.meteogrid.com/', 'https://geoserver.myclimateservice.eu/') where position('https://clarity.meteogrid.com/' in field_reference_path_value) = 1;
update node__field_reference_path set field_reference_path_value = replace(field_reference_path_value, 'http://services.clarity-h2020.eu:8080/', 'https://geoserver.myclimateservice.eu/') where position('http://services.clarity-h2020.eu:8080/' in field_reference_path_value) = 1;
|
@therter this is done, right? |
Yes, this is done and on the maintenance site, the url was also corrected. |
Once the Export of Geoserver layers from MTG to ATOS has been completed. We have to update all GeoServer URIs of respective resources. AFAIK @therter knows how to do it directly on the level of the database.
Furthermore, I've noticed that there a two ATOS GeoServer instances:
http://services.clarity-h2020.eu:8080/ still seems to cause problems with include in report functionality, since TLS is not enabled for services.clarity-h2020.eu.
Question: Will we move everything to geoserver.myclimateservice.eu? If not, https has to be supported for services.clarity-h2020.eu.
The text was updated successfully, but these errors were encountered: