anchor.diff:  
   == Miscellaneous
   
  -=== Security
  -
  -Celos is intended to be used inside a VPN, and by trusted developers.
  -
  -=== Time
  -
  -All times in Celos use the UTC timezone exclusively.
  +=== Related Tools
  +
  +Two similar, programmable schedulers:
  +
  +* link:https://github.com/airbnb/airflow[Airbnb Airflow]
  +
  +* link:https://github.com/spotify/luigi[Spotify Luigi]
   
   === The Celos Name
   
  
positive.code: Simple: It solves my use case.
  ....
  
  === Related Tools
  
  Two similar, programmable schedulers:
  
  * link:https://github.com/airbnb/airflow[Airbnb Airflow]
  
  * link:https://github.com/spotify/luigi[Spotify Luigi]
  
  === Acknowledgements
  
  Thanks to our in-house users and to the developers of the many fine
  
negative.code: A Celos workflow always has an Oozie workflow
  (`/wordcount/workflow.xml` in this case) as its "meat".
  
  If we were to receive data from two sources, say two datacenters in
  `/input/nyc` and `/input/lax`, we can define a helper function and use
  that to quickly define two workflows with the IDs `wordcount-nyc` and
  `wordcount-lax`:
  
  [source,javascript]
  ....
  