David Luecke

With the `authStrategies` (or if they are different `parseStrategies`) you set, the first one that applies will be used. E.g. if you have `[ 'jwt', 'preview' ]` for a REST...

You are right, there isn't too much documentation out there yet and we created https://github.com/feathersjs/feathers/issues/157 a little while ago to keep track of that. Here are some of my thoughts...

Definitely. And we could definitely use some help. Maybe lets gather first what we'd like to see in a guide and then make some demo applications?

Yes but why couldn't the other interested services also use websockets? We are thinking of adding other providers (e.g. for different messaging services) but for now websockets seem to be...

Nothing really prevents that, I'd say it's on you not to do that. It will only really be a problem if you define your models and relationships at the ORM...

I wrote more about how distributed authentication could be done in https://stackoverflow.com/questions/41076627/evaluating-featherjs-authentication-needs/41095638#41095638: There are several ways of splitting up services each with their own advantages and drawbacks. One generally important...

NODE_ENV has to be set to `production` via the Heroku CLI or in the application settings:

I noticed the same thing. I think I'll revert that PR and make a new generator release. Also, a Cookbook entry for Heroku deployment would still be a very welcome...

This looks like a good step, thank you. I am seeing the same error locally you can [see in CI](https://github.com/feathersjs/feathers/runs/6852371087?check_suite_focus=true#step:6:601): > Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib' is not defined by...

As a reference, there already has been a long discussion related to this three years ago in https://github.com/feathersjs/generator-feathers/issues/95 (and somewhere else that I can't find at the moment). The `hooks`...