-
-
Notifications
You must be signed in to change notification settings - Fork 753
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generator for scaffolding a feathers app #159
Comments
Work has started on this here: https://github.com/feathersjs/generator-feathers |
Since I need this anyway, I started working more on it in https://github.com/feathersjs/generator-feathers/tree/app-architecture. I think https://github.com/feathersjs/generator-feathers/tree/app-architecture/app/templates/src is a good start. |
Do we want to take cookie-parser off this list, since we'll be using tokens, now? |
Ya I think we can scratch out cookie parser. |
Sub generators. Refs feathersjs/feathers#159
Finally this is done! Closed by feathersjs-ecosystem/generator-feathers#49 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue with a link to this issue for related bugs. |
Since feathers is very modular it can be tough for a newcomer to get a handle on all the modules required for an app. We want to keep everything modular and flexible but still provide all the functionality you would expect in a real-time framework. We are inspired by, and run on top of Express after all!
So with that we should create a yeoman generator that scaffolds an application.
It should promp you for:
License(using Proprietary by default)URL(left to the user, we may pre-poulate with your-app.feathersjs.com)Author(left to the user)Whether it serves static content(should always as it's baked into Express)It should then generate the app with the following dependencies if the user answered yes to above questions:
body-parser
CORs
serve-favicon
compress
winston
feathers
feathers-config
(deprecated in favour of using your own)feathers-logger
feathers-hooks
feathers-authentication
(not ready, it's more of an advanced guide thing)feathers-sync
feathers-[database adapter]
feathers-[transport plugin]
A suggested folder structure would look like:
High Level Tasks Remaining
Twitter(not going to make it for this release. OAuth1 support won't make this release)The text was updated successfully, but these errors were encountered: