anchor.diff:  build.sh
   ```
   
  -Once that is done, you can  then begin to add SimplePaaS functionality, incrementally.
  -
  -To get a basic SimplePaaS system, install :-
  -
  -* Switch
  -* Container API
  +The SimplePaaS command line tool, `sp` is available for interacting with a SimplePaaS installation.
  +To install the platform, run `sp devinit`, this will install the minimal set of services to act as a PaaS on a single node.
   
   These components allow you to take existing Docker images, as normal, and securely deploy them to 
   the local Docker with declarative Service Injection, via the API.
  -
  -See ContainerAPI below for information on Service Injection.
  -
  -[use a restartable ambassador container to forward the traffic to the correct final point]
   
   ## Component Structure
   
  
positive.code: Each folder should contain a build.sh script that will execute whatever build steps are necessary.
  Build tools should be bootstrapped by this script and not assumed to be installed. (eg, using gradlew)
  
  The Artifact created must be TBD
  
  ### Container 
  
  Each Micro Service will be bundled into a container for deployment into SimplPaaS.  This process of bundling is 
  managed via a Dockerfile.
  
  Each container folder must contain a Dockerfile, and a unittest.sh
  
  The unittest.sh should run any and all infrastructure tests on this single container, for example using Vulcan Infrastructure
  Specifications.
  
  The unittest.sh should generate JUnit compatible result XMLs to output/ and pass through the exit result.
  
  The Dockerfile should contain the normal information to build the container, plus some meta data to indicate
  the required/ provided service dependencies
  
negative.code: RUN         apt-get update
  RUN         apt-get -y install redis-server
  EXPOSE      6379
  ENV PROVIDES redis:6379
  ENTRYPOINT  ["/usr/bin/redis-server"]
  ```
  
  This service indicates to the managing SimplePaaS components that it *provides* the redis capability, running on port 6379.
  This information will be used by platform to permit declarative service wiring and checking of runtime links between containers
  
  