very basic start for custom, user-provided routes (Issue #48)

- changes to psiturk-setup-example
   - now create a folder for the files to live in
   - includes a default 'custom.py' showing how to add custom routes
   - files moved around so that they can be copied easier (all reside in psiturk/example now)
oops, lost these files due to .gitignore
moving authentication out as a importable module for end-users

- users providing custom routes might want to password protect them (e.g., those providing custom views of data, etc...)
- this provides a class-based decorator which can do this
boom!  this works (easier than expected).  here's a nicer example to show how

- example custom.py script showing how to access various customizable features
- who want to write /calculate_bonus (?)
hides the default custom.py from the psiturk import path  (Closes #48)

kind of hacky, but works for now
log finished experiment and write time into endhit field in database
Disable gunicorn access log

It's probably not terribly useful for most people and clutters the server log (at all log levels)
version number bumped (try 2)
more protections for local debugging mode

- allows you to reload ad even if "fake" workerId has advanced to the experiment
Squashed commit of the following:  (closes #48)

commit 9e2bd6644f28aef3d9742bc3c375b8eb1dda8ec9
Author: Todd Gureckis <todd.gureckis@nyu.edu>
Date:   Tue Dec 10 00:24:49 2013 -0500

    hides the default custom.py from the psiturk import path  (Closes #48)

    kind of hacky, but works for now

commit f10b6ccfd1dd1fbe2ac983af6db4e8c9f7b445b9
Author: Todd Gureckis <todd.gureckis@nyu.edu>
Date:   Tue Dec 10 00:15:41 2013 -0500

    boom!  this works (easier than expected).  here's a nicer example to show how

    - example custom.py script showing how to access various customizable features
    - who want to write /calculate_bonus (?)

commit 81c86ecac932f4295ab31205520e121e8398a78e
Author: Todd Gureckis <todd.gureckis@nyu.edu>
Date:   Mon Dec 9 23:55:39 2013 -0500

    moving authentication out as a importable module for end-users

    - users providing custom routes might want to password protect them (e.g., those providing custom views of data, etc...)
    - this provides a class-based decorator which can do this

commit 5713e0be5e56284425b7dfd658e35ad1eb153fa9
Author: Todd Gureckis <todd.gureckis@nyu.edu>
Date:   Mon Dec 9 23:19:39 2013 -0500

    oops, lost these files due to .gitignore

commit 06f7c7c93d5da684cc17d9e648b31ae4c4202217
Author: Todd Gureckis <todd.gureckis@nyu.edu>
Date:   Mon Dec 9 23:15:33 2013 -0500

    very basic start for custom, user-provided routes (Issue #48)

    - changes to psiturk-setup-example
       - now create a folder for the files to live in
       - includes a default 'custom.py' showing how to add custom routes
       - files moved around so that they can be copied easier (all reside in psiturk/example now)
this is how version numbering is supposed to work
Merge remote-tracking branch 'origin/custom_routes' into dev

Conflicts:
	psiturk/version.py
closes #62

previously, custom.py was being compiled during setup tools into a .pyc (which shouldn't be a part of the experiment setup because it might not be binary compatible across machines).  now that custom.py is stored as custom.py.txt this is no longer an issue and we shouldn't delete the .pyc file.
gitignore was hiding the supporting libraries for the example. (closes #64)
actually this might be a better fix for the .gitignore issue
Fix keydown unbinding in example

Previous version adds an empty handler rather than removing original one.
starting to lay out skeleton for new command structure
Added completion to server command

Changed command names to reduce number of server commands with same starting letter, and added space to end of completions for easier two word completion.
added worker and hit completion
added help method to server command