anchor.diff:      ...
   ....
   
  +* `workflow.js` is the JavaScript file containing workflow definitions.
  +* `defaults.js` is a JavaScript defaults file containing variables and utility functions.
  +* `hdfs` is the Oozie workflow directory.
  +
  +If `WORKFLOW_NAME` is the value of the `--workflowName` argument, and
  +`HDFS_ROOT` is the value of the `--hdfsRoot` argument, and
  +`WORKFLOWS_DIR` and `DEFAULTS_DIR` are the Celos workflows and
  +defaults directories specified in the target file, respectively, then
  +the files will be deployed to the following locations:
  +
  +....
  +workflow.js -> $WORKFLOWS_DIR/$WORKFLOW_NAME.js
  +defaults.js -> $DEFAULTS_DIR/$WORKFLOW_NAME.js
  +hdfs/       -> $HDFS_ROOT/$WORKFLOW_NAME
  +....
  +
   === Target file
   
   A target file is a JSON file that describes a Celos and HDFS setup.
  
positive.code: |`--defaults`|Path|No|Defaults directory (defaults to /etc/celos/defaults).
  |`--logs`|Path|No|Logs directory (defaults to /var/log/celos).
  |`--db`|Path|No|State database directory (defaults to /var/lib/celos/db).
  |`--autoSchedule`|Integer|No|Interval (in seconds) between scheduler steps.  In not supplied, Celos will not automatically step the scheduler, and wait for POSTs to the /scheduler servlet instead.
  |===
  
  === Server HTTP API
  
negative.code: 
  == Celos CI Reference
  
  The celos-ci-fat.jar can be used to deploy workflow and defaults
  JavaScript files, as well as Oozie workflow directories automatically.
  
  The best practice for using Celos CI is putting a target file for each
  Celos installation in a central, SFTP-accessible location, and storing
  the target file's SFTP URL in an environment variable,
  e.g. `TARGET_FILE`.  Deploy scripts using Celos CI should then pass
  this variable as the `--target` argument to Celos CI, making them
  independent of the Celos installation.  See link:samples/quickstart[]
  for an example.
  
  ....
  java -jar celos-ci-fat.jar <arguments...>
  