Alex Kocharin

actually, that's not supported yet in `syn`: https://github.com/dtolnay/syn/issues/1502

> Seems like sending a PR to syn would be the way to go, then once that's merged we can use it... looks like it's already merged: https://github.com/dtolnay/syn/pull/1622

When the error is occured, current caret position is at 3:3. So parser expects something at 3:3, but can't find anything. I don't think this one is misleading, an end...

The last day of release being "8 years ago" should probably tell people as much about state of this project as a deprecation warning would. I'm happy to find that...

Looks like a bug, error message definitely looks odd. But I can't reproduce it. Is it still an issue? (sorry for the delayed answer, was on vacation)

Maybe two separate errors happened, and sinopia returns the first error occured, which happens to be 404. It is a bug indeed, because normally 404 is a success in this...

We're dealing with a lot of binary files (tarballs), and they need to be stored somewhere more or less efficiently. Mongodb will probably be a good choice because of gridfs....

Are there any modules for postgres/mongodb implementing standard node `fs` interface?

@SyntaxRules , I was thinking about it as a plugin, same as auth plugins. So kinda second option. You add something like: ``` yaml fs: sinopia-mongo-plugin: database: blah password: blahblah...

What is the current status of this pull request?