[Geoserver-users] Advice for tracking geoserver changes through SCM & synchronize multiple Geoserver instances

Dear all,

I’m currently investigating how to integrate the management of the Geoserver data directory in a SCM to track changes, and synchronized between multiple instances (development, test, production)

First of all, I’d like to get advice on which part of the geoserver data directory could be synchronized through SCM, and those directories that should be out of synchronization (e.g. for security or space reasons), being aware that the content of this tracked data directory could exposed in a repository that can be accessed publicly (e.g. Github).

I would also like to get feedback from users/organizations that eventually have already investigated solutions to track Geoserver changes, possibly in a multi-environment context (development, test & production)

Thanks a lot in advance for the advice you could provide,

Kind regards,
Emmanuel

btn_in_20x15.png

···


Emmanuel Blondel
GIS Consultant
Engineer in Agronomy & Environment

Geographic Information Systems
in Agronomy - Environment - Fisheries
Email: emmanuel.blondel1@anonymised.com - Emmanuel.Blondel@anonymised.com
View my LinkedIn profileView my LinkedIn profile

Hi Emmanuel,
I think the first thing is to make sure the data is separate from the data directory. You’ve probably already seen this page but just in case:
http://docs.geoserver.org/stable/en/user/production/data.html

btn_in_20x15.png

···

You may also want to take a gander at: http://docs.geoserver.org/stable/en/user/security/passwd.html

There are probably other things (hopefully others (more knowledgeable!) will chip in), but hopefully that’ll get you started.

Cheers,
Jonathan

On 11 June 2014 16:55, Emmanuel Blondel <emmanuel.blondel1@anonymised.com> wrote:

Dear all,

I’m currently investigating how to integrate the management of the Geoserver data directory in a SCM to track changes, and synchronized between multiple instances (development, test, production)

First of all, I’d like to get advice on which part of the geoserver data directory could be synchronized through SCM, and those directories that should be out of synchronization (e.g. for security or space reasons), being aware that the content of this tracked data directory could exposed in a repository that can be accessed publicly (e.g. Github).

I would also like to get feedback from users/organizations that eventually have already investigated solutions to track Geoserver changes, possibly in a multi-environment context (development, test & production)

Thanks a lot in advance for the advice you could provide,

Kind regards,
Emmanuel


Emmanuel Blondel
GIS Consultant
Engineer in Agronomy & Environment

Geographic Information Systems
in Agronomy - Environment - Fisheries
Email: emmanuel.blondel1@anonymised.com - Emmanuel.Blondel@anonymised.com
View my LinkedIn profileView my LinkedIn profile


HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems


Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

I will back up with Jonathan, backup the settings not the data.

Punting your data directory onto of git works for a simple clean setup.

I have also seen a team use the REST API to extract a configuration for storage (the advantage being that they could reconfigure a new node). It was pretty advanced and not the the faint of heart - but they enjoyed it.

Jody

btn_in_20x15.png

···

Jody Garnett

On Thu, Jun 12, 2014 at 6:40 PM, Jonathan Moules <jonathanmoules@anonymised.com> wrote:

Hi Emmanuel,
I think the first thing is to make sure the data is separate from the data directory. You’ve probably already seen this page but just in case:
http://docs.geoserver.org/stable/en/user/production/data.html


Taking a quite look at mine I’d suggest everything could go into a version control system except maybe:
/security/ and subdirectories - it has a number of password things in it including usernames/passwords. The later may be encrypted, but still probably don’t want to share them.
datastore.xml files within /workspaces/ - these contain connection details for your datastores, at least for Oracle they do. The passwords should be encrypted (if you’ve enabled that), but still.

This transmission is intended for the named addressee(s) only and may contain confidential, sensitive or personal information and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.

HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems


Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

You may also want to take a gander at: http://docs.geoserver.org/stable/en/user/security/passwd.html

There are probably other things (hopefully others (more knowledgeable!) will chip in), but hopefully that’ll get you started.

Cheers,
Jonathan

On 11 June 2014 16:55, Emmanuel Blondel <emmanuel.blondel1@anonymised.com> wrote:

Dear all,

I’m currently investigating how to integrate the management of the Geoserver data directory in a SCM to track changes, and synchronized between multiple instances (development, test, production)

First of all, I’d like to get advice on which part of the geoserver data directory could be synchronized through SCM, and those directories that should be out of synchronization (e.g. for security or space reasons), being aware that the content of this tracked data directory could exposed in a repository that can be accessed publicly (e.g. Github).

I would also like to get feedback from users/organizations that eventually have already investigated solutions to track Geoserver changes, possibly in a multi-environment context (development, test & production)

Thanks a lot in advance for the advice you could provide,

Kind regards,
Emmanuel


Emmanuel Blondel
GIS Consultant
Engineer in Agronomy & Environment

Geographic Information Systems
in Agronomy - Environment - Fisheries
Email: emmanuel.blondel1@anonymised.com - Emmanuel.Blondel@anonymised.com
View my LinkedIn profileView my LinkedIn profile


HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users