Fix backwards incompatibility.
Merge pull request #33 from peerlibrary/backwards-compatibility

Fix backwards incompatibility
Allow the user to specify an encoding for the buffer when storing on the server.

The current implementation was using 'utf8' as that is the default when
dealing with Node buffers. However, I wanted to store images taken from
an HTML canvas element via canvas.toDataURL(), which returns a base64
encoded png as a data URL.

Note: I have done a few simple tests, and this code appears to work
with 'utf8' and 'base64' encodings. However, other encodings are
untested and may or may not work (unsure if MongoDB places any
limitations on acceptable char encodings or not).
File encoding is stored in the fileRecord.

File encoding specifies how the buffer should be read (using
buffer.toString) and written (buffer.write).
Updated documentation (added encoding to the fileRecord structure).
Typo fix.

Not sure how that got there.
Merge pull request #36 from nhibner/devel-buffer-encoding

Option for file encoding
Add credit to README

Credit @nhibner, @mitar, @petrocket
Update README.md
Minor text edits
more text edits
Resolve conflict
Update README.md

Added credit to @emgee3, thanks!
Fixed issue #40

On new apps the bundle static folder dont exists - collectionFS could
not create a symlink.
* added a check + create for the static folder
updated scope for serverConsole

* removed scope limit
* minor refractor
* added supress publish warning when autopublish
bump version
Fixed issue #41

* Minor fix due to new option `encoding`
Bump version 0.2.3
Extensively revised README

Better organization, rewording, clarified and simplified some examples
Remove fetch