Closed bcardarella closed 9 years ago
@rwjblue my understanding is that the current functionality requires you to maintain the entire blueprint set somewhere. I don't think this is a good approach. Instead there should be a simple set of rules for changes that should be made after the app is generated normally.
You would invoke the main app
blueprint, then make the smallish modifications you need in your custom blueprint. The pattern of invoking other blueprints from within a blueprint is one that is done often in the codebase already (ember g resource
generates routes, controllers, templates, etc).
This works!
I believe this is already implemented:
There is still a but of work if you want this to work from an internet hosted
.tar.gz
file though (I don't believe that is implemented yet), but it could also be relatively easily wrapped in a two line shell script or something...