The history... we remember the days when we thought that YiiBoilerplate was a good fit for any project. They were good days, but we were being naive.
Every project has different needs, and it’s those needs that set the requirements. Also, lets be realistic, if you were to develop a project where only the frontend UI with a small admin section was needed, YiiBoilerplate was overkill. In the end, people had to remove unneeded folders, the configuration was unnecessarily complex, a lot of people were not certain where to place the components and there were many other issues.
At 2amigOS! we were slamming our heads down on our keyboards trying to figure out what was the best way to provide a project boilerplate that could fit everyones needs. We soon realized and agreed that composer was the best way to go as a dependency manager (special shout-out thanks to Mr Tobias Schmunk, the guy behind Phundament for his great work and ideas), but we did not want to provide a fixed structure nor a set of extensions, again. Otherwise, we would just be putting a fresh coat of paint on the same problems. We wanted to give the power back to the developer to pick and choose based on their own needs. You know your project the most, so you should be able to set your own desired folder structure. You should be able to select which extensions you want to have pre-installed. And that, my amigos, is how Yiinitializr was born!
Yiinitializr is technically still in beta (?). Why? Because we believe that we need your feedback, yes you, from the Yii community, to make Yiinitializr right for all of us. You’re going to be using it, often (c’mon, you know you will...), so why not have a say in whether it’s enough or not... in what else it should or should not provide.
Okay, okay.. enough talk... now, let’s see how this baby works!
Yiinitializr is extremely easy to use. It is composed of only one page that will ask you three simple things:
Unzip, wherever you want your project to be, then (no, we are not going to tell you how to setup your database configuration. This is just a gentle reminder that you need to do that next...). Ahem... make your database configurations. Now, run the following commands inside the unzipped project’s root:
// make sure you have the latest version of composer php composer.phar self-update // run install php composer.phar install
Now, relax and love it! (or hate us, but keep it to yourself... really, all that negativity focused on us? We’re amigos! Come and share in the enchiladas... click on the docs below the templates to go to that github place and vent there...)
So, now you’re saying, “yeah, man... that is simple, but what are the template differences?”. We thought you’d never ask:
“But I want more details!” Yes, we agree, and this a great point to start the share of some knowledge. We know that once you download any of the template boilerplates you’ll start wondering what’s going on here. What the heck is this way of initializing applications? Check out the yiic.php or the index.php scripts within any of the application’s folder. See what we are doing. There is another surprise extension within, the Yiinitializr components. A set of classes that makes for a really easy way you can configure and install a project.
More documentation and discussion will be coming... we promise. We just wanted to let you play and react a little, first.
web development has never been so fun