anchor.diff:  ----
   ====
   
  -== Text search using an application hosted by Passenger
  +== Text search using a web application hosted by Passenger
   
   This setup has more dependencies than the CGI example. The upsides are e.g. stateful execution, better performance, more versatile.
   
  
positive.code: # generate html docs from all 1.x tags
  giblish -t "^v1" -m giblish html_docs
  
  # opy the cgi template provided in the giblish gem to the directory
  # for the html docs.
  # The template is named 'gibsearch.rb' and resides under 
  # 'web_apps/cgi_search' relative to the dir of the installed
  # giblish gem. 
  # The below uses bash to find the template, copy and rename it to 
  # 'gibsearch.cgi' to make it smoother to use the cgi func of webrick.
  cp "$(dirname $(gem which giblish))/../web_apps/cgi_search/gibsearch.rb" html_docs/gibsearch.cgi 
  
  # copy a boot-strap script for Webrick from the giblish gem
  
negative.code:  . gibsearch.rb - a naive implementation of a CGI script in ruby that uses the helper classes provided by giblish to retrieve and format an html response triggered by a search request to a web server.
   . wserv_development.rb - a naive implementation of a boot-strap script for an instance of Webrick, a web server written in ruby, that serves html pages on localhost:8000
  
  IMPORTANT: The template scripts in giblish are provided as examples and are not tested in any form of production use.
  
  .Using CGI and ruby's built-in Webrick server
  ====
  This is the most basic example, it assumes that all documents and tools are run on a local machine. To publish documents to the world, you would replace Webrick with Apache, Nginx or other, more production-friendly web server.
  
  [source,bash]
  ----
  