anchor.diff:  === Elasticsearch
   
   The GeoRocket distribution contains a version of Elasticsearch that will
  -automatically be started together with GeoRocket. You can disable this
  -behaviour and use a remote Elasticsearch instance instead.
  +automatically be started together with GeoRocket by default. You can disable
  +this behaviour and use a remote Elasticsearch instance instead.
   
   Set the following configuration items to disable the provided Elasticsearch
   instance and to configure the host and port of the remote one:
  
positive.code:   _(default: true)_
  | `true` if GeoRocket should launch the provided Elasticsearch instance. `false`
  if it should connect to an existing instance.
  | *georocket.index.elasticsearch.host* +
    _(default: "localhost")_
  | Elasticsearch host address
  | *georocket.index.elasticsearch.port* +
    _(default: 9200)_
  | Elasticsearch TCP port
  | *georocket.index.elasticsearch.javaOpts* +
    _(optional)_
  | JVM options for the embedded Elasticsearch instance. This configuration item will only be taken into account if `georocket.index.elasticsearch.embedded` is `true`. It can be overridden through the environment variable `ES_JAVA_OPTS`. See the https://www.elastic.co/guide/en/elasticsearch/reference/current/setting-system-settings.html#jvm-options[Elasticsearch documentation] for more information about `ES_JAVA_OPTS` and reasonable values for the https://www.elastic.co/guide/en/elasticsearch/reference/master/heap-size.html[heap size].
  
negative.code:     index:
        elasticsearch:
          embedded: false
          hosts: ["192.168.0.100:9200"]
  
  Replace the connection string `192.168.0.100:9200` with the actual hostname (or
  ip address) and port of your existing Elasticsearch instance.
  
  ==== Configuration
  
  