View more context



oh man, knew it had to be something dumb! thanks @alt


looking at doing it myself, wondering if it is worthwhile


@nickspiel: Funnily enough I was thinking about that generator this morning and wondered whether it was still usable? In answer to your question, no, I’m not. But that’s largely due to the fact that I don’t do that many SS sites these days. TBH though I think Yeoman possibly overcomplicates things a bit. It’s yet another ‘thing’ to keep up to date. These days most things can be easily set up/pulled in using Composer, and for my front end build I have a base starting point that includes a Grunt workflow and some core SCSS/LESS stuff, which I just drop into a project.


what we do @nickspiel is have a base Silverstripe project that is a form of the 'composer create project’ that Silverstripe have. In there we have a list of base modules, a vagrant machine config and the base of our internal front end framework. We can get going on a project in about 10 min!


Vagrant box. Basic install, update composer.json with what I want. Composer Update, grab coffee, and another one. And probably another one.


I put together my own yeoman generator today and am really loving the prompt based config. Vagrant boxes sound like great option too, we have an project on at the moment to move over to vagrant boxes. I can’t wait for this to happen. We will probably revise this yeoman generator when this happens.


firesphere: i'm using the preconfigured zauberfisch vagrant box for local development.