anchor.diff:  
   giblish setup::
    . Install ruby on the _Server_ (a version no more than 18 months old)
  - . Install giblish on the _Server_ using `gem install giblish`
  + . Install giblish on the _Server_. See e.g. <<:docid:G-001>>
   
  -git and gitrepo setup::
  +git and git repo setup::
    . Install git on the _Server_.
    . Setup the *bare* _Main Repo_ on the _Server_ by either.
    .. Copy a bare repo you already use to the _Server_ file system.
  
positive.code: A running instance of Jenkins and one or more defined build jobs that use giblish to build the HTML documents.
  
  Web Server::
  Apache, Ngnix or other web server that provides clients with HTML pages located somewhere on the file system on the server (e.g under /var/www/... )
  
  ==== Pros & cons
  
  Pros::
   * Using Jenkins enables a lot of flexibility and scaleability. You can setup multiple Jenkins agents to increase performance, you can define many build jobs where each job builds either a particular branch from a particular git repo or many branches from one or many repos.
  
negative.code: ====
  [source,bash]
  ----
  include::../../scripts/hooks/post-update.example[]
  ----
  ====
  