Looks interesting. Seems it might be simpler than express MVC in some ways. You might consider adding how to connect to various databases/using an ORM in the documentation.
I didn't take an in depth look at roosevelt, but it also doesn't appear to have generators (for controllers/models etc). One of the bad things about some MVC frameworks that lack generators is the copy pasta style development
We decided against staging a database (and especially an ORM) by default, as it would make the framework a bit too opinionated, but we're certainly not against adding support for it as an off-by-default option in the generator to add in a bunch of common db configs.
Isnt that just a generator for the app itself? I'm talking about the scaffolding/generating that .NET/emberjs do when you want to do something boilerplatey.
As for the DB issue, I mean't show how you can connect to a DB in the docs
Gotcha, yeah, we consider both out of scope of the project for now. Roosevelt has no opinion on what you should do for your frontend (thus no discussion of client-side JS stuff) and no opinion on what you should do for your database (thus nothing in the docs yet). Down the road we anticipate adding docs and generator options to add the necessary boilerplate for common approaches to those things though, but it is unlikely we will ever prescribe a default when it comes to either one of those things, given that the right client-side framework (if any) for the job and the right database (if any) for the job depends heavily on what kind of app you're building.
I'm still not 100% sure you understand my comments. I wasn't suggesting you choose a frontend framework or DB for the user. Just show how to connect to a DB of their choosing. Also, if you use the yeoman generator and choose MVC you get controllers, views, models - or something along those lines, right?. So my suggestion was: if a user chooses MVC, it would be nice to be able to do something like: yo roosevelt books. And it give you a books controller, view, and model. Or something similar to that. So that each time they want to add a resource, they dont have to perform the same action (manually creating those files) over and over again. They can just use yeoman to speed up the workflow.
Implied in that issue is the notion that one day it would be nice when running the generator to be able to tell it you want to opt-in to a PostgreSQL config, or MongoDB, or SQLite, as well as populate some boilerplate MVC files for some common use cases, e.g. something like books as you say, so as to have an end-to-end example to follow.
At present, if you follow the advanced mode in the generator, some of the questions you get include:
...
? Which CSS preprocessor would you like to use? LESS
? Which JS compiler would you like to use? UglifyJS
? Where should data model files be located in the app's directory structure? mvc/models
? Where should view (HTML template) files be located in the app's directory structure? mvc/views
? Where should controller (Express route) files be located in the app's directory structure? mvc/controllers
? Do you want to use a HTML templating engine? Yes
? What templating engine do you want to use? (Supply npm module name.) teddy
...
I presume down the road, some questions we could add would include:
? Do you want to include a database config? [N/y]
[if Y] ? Which database config would you like to prepopulate? [pg/mysql/mongodb/sqlite/etc as possible options]
? Would you like to prepopulate the app with some MVC examples? [Y/n]
[if Y] ? Which examples would you like to prepopulate? [todo list/books/etc as possible options]
I didn't take an in depth look at roosevelt, but it also doesn't appear to have generators (for controllers/models etc). One of the bad things about some MVC frameworks that lack generators is the copy pasta style development