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.
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 <[email protected]> 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: [email protected] - [email protected]
> [image: View my LinkedIn profile]View my LinkedIn profile
> <http://fr.linkedin.com/in/emmanuelblondel1>
>
>
> ------------------------------------------------------------------------------
> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
--
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
