Hi,
I'm trying to decide on the best way to properly version control the xml
configuration files for a Geoserver cluster (~latest version). Currently
the cluster is deployed on AWS so we are using EFS to sync the files
between instances and I am planning on enabling the clustering plugin.
However, I'm wondering if there is any best practice or suggested way to
handle all of our configuration files. Ideally, we would use Postgres as
the actual configuration source and not have any files stored on disk at
all - but second to that, I'm thinking a simple git repository with a
background process that listens for changes and commits them is a good
solution.
Eventually, my hope is to have our GIS team be able to make changes through
the admin portal in a staging environment, test and QA this set of changes,
create a snapshot, and then deploy this snapshot to production (of course
we will then re-seed all layers in geowebcache after deploying).
I would love ideas or recommendations on the best way to do this!
Thanks!
--
Chris Roth
cjroth.com <http://www.cjroth.com>
_______________________________________________
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
