Add initial chef server configuration

[tdooner]

This adds some basic server configuration as specified in the Chef recipe DSL, which is a good starting point for getting a production-hardened instance of clientcomm running.

Chef works by allowing you to specify a set of "resources" in recipes with certain properties (e.g. file ownership, chmod) and then an action to perform on that resource to bring the machine into convergence (e.g. "create", "delete").

The Chef TODO list is still roughly:

• [x] Non-root user that the app will run as
• [x] Installing a fixed version of nodejs
• [x] Downloading a copy of the code
• [ ] Nginx reverse proxy in front
• [ ] Systemd init script

(although there is no real reason this commit could not be merged. It works.) And then we will have to figure out if we want to use an application deployment framework like capistrano/a nodejs equivalent, or just roll our own, which wouldn't be too difficult for the short term.

[codecov-io]

Codecov Report

Merging #349 into master will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #349   +/-   ##
=======================================
  Coverage   63.14%   63.14%           
=======================================
  Files         108      108           
  Lines        4160     4160           
  Branches      452      452           
=======================================
  Hits         2627     2627           
  Misses       1533     1533

Impacted Files	Coverage Δ
app/lib/em-notify.js	60.37% <ø> (ø)	:white_check_mark:

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update cd6a160...80404c3. Read the comment docs.