Hi Peter,
while at the moment we are deploying configuration by simply copying files from server to server and then letting GeoServer reload its configuration, we are now writing a tool that uses database tables as a source to syncronize configuration of all of our GeoServer instances using the REST interface. This tool then can be configured to use different connection strings etc. in different environments. It also handles the security configuration and has a "debug only" setting for layers that are not to be published to production yet. We chose this way as we are already using the source database tables to control the client interfaces and the search engine of our (Web-)Gis applications and didn't want to go on with having duplicate work when configuring layers. Best regards Daniel From: Peter Smythe <g...@smythe.co.za> Sent: Freitag, 12. August 2022 17:01 To: GeoServer Mailing List List <geoserver-users@lists.sourceforge.net> Subject: [Geoserver-users] Copying GeoServer configurations between various environments (dev -> staging -> prod) Hi all GeoServer admin users I wonder if I can poll you to find out how you manage or copy your GeoServer configurations between various environments like dev -> staging -> production? We make use of JNDI to extract the database credentials out of the GeoServer data directory and into the Tomcat container. https://docs.geoserver.org/latest/en/user/data/database/jndi.html We can make use of setting certain parameters like the data directory and proxy URL in the WEB-INF/web.xml file: https://docs.geoserver.org/master/en/user/datadirectory/setting.html#context-parameter Similarly, we use ENV_PROPERTIES to parameterise various ${authkey_provider_url}, etc https://docs.geoserver.org/latest/en/user/datadirectory/configtemplate.html This way, the configuration files for various environments can be identical. (We also previously made use of the jdbcstore/jdbcconfig extensions which store the above XML file contents in database tables, but we found that it was less accessible and didn't really work for us.) However, perhaps you want to take a new configuration live but you have a new workspace/layer/style in dev that mustn't go live yet. How do you exclude it? Because the configuration is all just XML files, they can be treated and manipulated as source code, perhaps using Git branches and Merge Requests. Does anyone do this? If not, why not? What other ways have you found to manage your various GeoServer configurations? Thank you Peter
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
