Gabriel Roldan
Gabriel Roldan
Starting up several geoserver instances lead to race conditions, especially when loading from an empty data directory or jdbcconfig database. These have been fixed on the following branches, and need...
Remove the gzip filter from the services, and let compression be handled by the gateway e.g.: ```yaml server: port: 8080 instance-id: ${spring.application.name}:${spring.application.instance_id:${spring.cloud.client.ip-address}}:${server.port} compression: enabled: true mime-types: - application/xml - etc...
Make it ready to deploy on k8s. Probably replacing `config` and `discovery` by kubernetes native services
Setting `management.endpoint.shutdown.enabled=true` to manually shutdown a service is not enough, a SpringBootApplication exit code generator and context listener needs to be added to the JVM would exit. Then `POST /actuator/shutdown`...
Add support for [AWS S3-hosted GeoTIFFs](https://docs.geoserver.org/latest/en/user/community/s3-geotiff/index.html) as a spring boot autoconfiguration
[backup-restore](https://docs.geoserver.org/latest/en/user/community/backuprestore/index.html) would be great for migrating configurations from a vanilla geoserver data directory to a gs-cloud instance, as it may be using some other catalog/configuration backend (e.g. jdbcconfig)
Depends on #80, revisit after it for further insights on the approach
`org.geoserver.wms.capabilities.LegendSampleImpl.clean()`, called by the constructor: ```java private void clean() { for (StyleInfo style : catalog.getStyles()) { synchronized (style) { Resource styleResource = getStyleResource(style); Resource sampleFile; try { // remove old...