murk/ command line files consumed by CLI (Closes #25)
Deprecate dashboard.
Deprecate dashboard.

- Delete dashboard and supporting files
- Comment out dashboard references in `psiturk-shell.py`
Revert "Deprecate dashboard."

This reverts commit aacdeb7d66d9555db30cd42414dd32bc8727afd8.
Deprecate dashboard.
Remove needless system file.
moving dashboard to a feature branch (follow up)

- removed Cakefile
- removed psiturk-dashboard from setuptools
- updated psiturk to run CLI by default
- remove static/ and templates/ directory accidentally introduced on last commits
- minor edits
updated MANIFEST.in
Make PEP8 compliant.
Merge branch 'dev' of github.com:NYUCCL/psiTurk into dev

# By Todd Gureckis
# Via Todd Gureckis
* 'dev' of github.com:NYUCCL/psiTurk:
  updated MANIFEST.in
  moving dashboard to a feature branch (follow up)

Conflicts:
	psiturk/psiturk_shell.py
removing dashboard parameters
Merge remote-tracking branch 'origin/dev' into ad_server

Conflicts:
	psiturk/psiturk_shell.py
updates to README to reflect CLI and Secure Ad Server features
ignore static and template folders if they are accidentally created in your repo by running psiturk-setup-example
adding configuration options for Ad server
replacing ambiguity of "code_version" config option to be sure it is the experiment version not psiturk code base
'support_ie' is conceptually a feature of the Task/Experiment rather than server or hit
no need to restart server when config parameters change

if config options are initialized at server start then later if we make PsiTurkConfig auto-reload on changes these won't be visible inside the experiment server.
- update config options by direct queries to config class
HIT_lifetime redundant with being in section "HIT Configuration"
better modularity for MTurkServices

- MTurkServices previously strongly depended on PsiTurkConfig
- Changes make it so all arguments to MTurkServices are specified via an API rather than assuming a PsiTurkConfig instance variable
- means amt_services can be more easily imported into another project, etc...
- also since it is a command-like interface, everything should be a parameter more or less set at the time the function is called rather than in a config file which might be loaded only at startup