process.env converts all values set into strings,
so its better to just not set it.

- Windows doesn't have signals, so process.on("SIGINT") throws
- changing process.env.PATH is a bad idea

run_locally should work well with CONFIG_FILES (not overwrite it so you can pass in extra config on the cmd line

The `static` process has been added to handle cachable resources and views, so
code relevant to serving those resources has been removed from `browserid`.

The `router` heartbeat now depends on both `browserid` and `static` processes being ok.
`router` now forwards wsapi writes to `dbwriter`, reads to `browserid`, and errors on unkown
or internal wsapi requests. The wsapi setup for `browserid` no longer handles forwards, though
some wsapi operations may trigger a forward to `dbwriter`.

optimize backend unit tests by starting all daemons in parallel, and then starting router.  issue #1803

Change browserid.org urls to persona.org, introduce static.login.persona.org for all static resources.

always run our little node HTTP proxy locally to constantly test HTTP proxy support which we'll have in production - issue #904

when running locally, SHIMMED_PRIMARIES set for all daemons (so dbwriter can interact with primaries too)

implement a more generic mechanism to enable local testing and development of primary support - allow SHIMMED_PRIMARIES to be provided which stuffs a auth url, provisioning url, and public key in our cache

implement a more generic mechanism to enable local testing and development of primary support - allow SHIMMED_PRIMARIES to be provided which stuffs a auth url, provisioning url, and public key in our cache

move generation of ephemeral database names (used in perf/unit testing) to a higher level and out of core code.  also, emphemeral database cleanup is now a responsibility of the harness running the software (test harness, or run_locally.js).  This fixes race conditions in unit tests that restart daemons (closes #557) and simplifies running local performance tests (issue #504)

when starting up processes for local development or under the test harness, start them serially waiting for each process to bind before starting tests.  issue #556

implement graceful process shutdown, and clear logging as to the reason why processes are terminating.  include winston handling of uncaught exceptions.  this all goes into a library that all of our processes use.  closes #529

add the dbwriter process.   it's not yet hooked up, but starts up and runs, and included in health check.

implement graceful process shutdown, and clear logging as to the reason why processes are terminating.  include winston handling of uncaught exceptions.  this all goes into a library that all of our processes use.  closes #529