serializing modify the response's content type
Dancer::P::Bcrypt recomends Dancer::P::Passphrase
allow the setting of the 'views' directory, like stated in documentation
Implement Dancer2::Test file uploads
FileUtils: Use a tempdir for the path_or_empty on an existing dir test.

'/tmp' does not exist on all systems, use a tempdir instead. Ref #194
Fixes Dancer vs Dancer2 consistency in Plugin.pm

* Line 157 was the main confusion.  "supports only Dancer2 1"
* Changes the other ``Dancer2`` pod/comment references to ``Dancer`` or ``Dancer 2`` as appropriate.

Does this look consistent/correct to the rest of you?
Mock open_file in D2::Core::Request::Upload namespace in test

On most platforms altering the coderef for D2::FileUtils::open_file
via glob assignment doesn't alter references where that code has been
imported into other namespaces, such as D2::Core::Request::Upload.
Win32 is one exception; in which case D2::Core::Request::Upload::open_file
was actually being mocked, highlighting a broken test case.

Mock D2::Core::Request::Upload::open_file to always croak (rather than
returning 0 and expecting it to behave like a file handle), and undo
the mock once finished that portion of the test. Ref #194.
Merge pull request #205 from blabos/master

Dancer::Plugin::Bcrypt marks itself as deprecated in favor of Dancer::Plugin::Passphrase
Merge pull request #214 from spazm/patch-1

Fixes Dancer vs Dancer2 inconsistency in Plugin.pm
Merge pull request #212 from shumphrey/dancer2-test-files

Implement Dancer2::Test file uploads
Indentation fix in documented example
Missing closing quote in doc example
fix to "Internal Server Error: Can`t locate object method "new" via package "Dancer2::Handler::File" (perhaps you forgot to load "Dancer2::Handler::File"?) at.. Dancer2/Core/App.pm in sub send_file arround my $file_handler = Dancer2::Handler::File->new" when issued a send_file with route_handlers: {} in config.yml
Give Dancer2::Test the ability to handle multiselect inputs

Dancer2::Test treats key => value params as always being scalar values.
However, it is possible to send multiple values per key in an http form.
multiselects/checkboxes etc. This gives Dancer2::Test the ability to
handle that (Dancer2 supports this fine, it's just the tests that don't)
gitignore: ignore new Dancer2-* instead of old Dancer-2.0
first stab at porting shining new script/dancer2 from D1
make introduction more fluid
more wording and remove unnecessary use
remove prereq Digest::SHA1 see gh193
Merge pull request #225 from mokko/pr/gh193

Remove prerequisite Digest::SHA1, see GH193.