anchor.diff:  
   Test to see if Funcation is running by pointing your browser to http://localhost:3000 .
   You should see a message like: `No Swagger Defined. Unable to route request`. This
  +is because there's no application connected to Funcatron. So... let's create an app.
   
   === Create a new project
   
  
positive.code: You can create `ServiceVendorBuilder` instances for any `type` and, boom, have access to those services
  based on Execution Properties.
  
  == Execution Properties
  
  == Funcatron Swagger File
  
  == The Build File
  
  == Packaging your Func Bundle
  
  
negative.code: The code prints some messages and connects to the
  development-time Funcatron instance in the Docker container.
  
  This code is useful for you to set up your IDE to do debugging, etc. while
  you run a mini version of Funcatron in a Docker container. What does it do?
  
  It makes a connection to the Docker container running mini-Funcatron. When mini-Func
  gets an HTTP request, it packages the request up and forwards the request to the
  app which is likely running in your IDE. You can see output, set breakpoints, and generally
  rapidly update your app.
  
  Also, given that your Funcatron apps should be small, recompile times should be short so you
  can quickly cycle and quickly build your app.
  
  If you're using a language or a development environment that allows
  dynamic code reloading (e.g., Clojure or https://zeroturnaround.com/software/jrebel/[JRebel])
  the `funcatron.yaml` (Swagger file) and the exec_props (runtime
  properties) will reflect the current values... update them
  at will.
  
  