Wes Roberts

Thanks for the explanation @mhallin. We should probably mention this front-and-center on the README.md as right now it reads as though the proper event will be forwarded. > A simple...

It would be nice if we could use the `Authorization: Bearer {token}` header instead of a GET param. For example, when using bash + wget, it's very easy to add...

I also have this problem, using macOS Sierra 10.12.4, Vagrant 1.9.1, and VirtualBox 5.1.14. Not using Vaprobash at all. So, Vaprobash is probably not the culprit. I just found this...

?

> ...from the spec I couldn't see how paths would be chosen if both match the request, and both use templates in the path. Your example may violate this stipulation:...

It seems that, even though we *can* conceive of tricky ways to resolve various types of ambiguity, avoiding it entirely would strengthen the rigorousness of the spec, ensure better interoperability...

You can fix this by specifying the events you want to forward, e.g. ```ruby config.vm.synced_folder ".", "/app", fsnotify: [:added, :modified] ``` Perhaps we should make `[:added, :modified]` the default?

No, using Ubuntu :( Really love the work you've done on MusikCube though. I use it every day.

Thanks @arantebw, it looks like this is the clean way to solve the issue. The core filepond code states that they plan to transition from `ActualFileObject` to the native `File`...

+1 would appreciate if the opacity control was more discoverable.