David Luecke

I think that makes sense. I've been meaning to add more features around that for the next version anyway (built-in token revocation strategy, refresh token) so this would fit in...

Closing this since the best solution is indeed using schemas in a [v5 app](https://dove.feathersjs.com/)

Do you have a link to your fork? For `@feathersjs/express`, middleware needs to be passed to the express app and service objects to the Feathers app. This is done in...

`feathers-sync` does not require sticky sessions. It assumes however that once a client has established a websocket connection it will stay connected to the same server for the entire connection....

That can be solved with what is described [how to use Socket.io in a Cluster](http://socket.io/docs/using-multiple-nodes/#using-node.js-cluster) though right? Feathers doesn't do anything that should interfere with that module.

This is documented in the FAQ at https://docs.feathersjs.com/help/faq.html#why-are-queries-with-arrays-failing

Ah sorry about that. It sounds like the `arrayFormat` should always be `brackets` when using `qs` then?

Is there documentation how to implement this?

Oooh... found it in the [npm init](https://docs.npmjs.com/cli/init) documentation. Basically you create a `create-feathers-app` repo and then can use `npm init feathers-app`.

Well, it doesn't exist yet. When it does yes, it probably will.