anchor.diff:  
   === Other
   
  +Most configuration options should be sufficiently annotated in the example configs to explain their purpose, a few others are worth briefly expanding upon.
  +
   ==== Hostname
  +
   ```json
   { "hostname": "localhost" }
   ```
   The hostname to bind to.
   
   ==== Endpoint
  +
   ```json
   { "endpoint": "mynode.local" }
   ```
  
positive.code: You'll need to have a valid JSON config (see following sections), and build apiman with Java 8 (`mvn clean install`):
  
  ```shell
  java -jar target/apiman-gateway-platforms-vertx3-1.2.0-SNAPSHOT-fat.jar -conf <path-to-your-config.json>
  ```
  
  Replace `1.2.0-SNAPSHOT` with the version you built.
  
  == Configuration
  
  
negative.code: NOTE: Verticle count only defines the number of verticles deployed in a given JVM instance (i.e. per `java -jar apiman<...>.jar -conf <...>`). How many deployments, and hence total number of verticles exist within your overall cluster is entirely up to you.
  
  ==== HTTP
  
  Plaintext HTTP entry-point, with no transport security. Turn off by reducing count to zero.
  
  ==== HTTPS
  
  Encrypted HTTPS entry-point, with TLS. Turn off by reducing count to zero.
  
  ==== API
  
  Hosts the apiman gateway API, which is typically used by the apiman manager to drive the gateway. For instance, publishing and retiring APIs, Contracts.
  
  === Gateway API Authentication
  
  NOTE: This only relates to apiman's Gateway API; it is *unrelated* to auth of traffic transiting the gateway.
  
  ```json
  {
  