For that you can configure the Gii module to run from the backend itself. In other words, in backend/config/main.php. Then run Gii from backend/index.php?r=gii
Just a tip for you people who do not run your dev server on localhost:
If you are not running Yii on localhost you need to add an ip filter rule to get access to the Gii module. By default Gii only allows connections from localhost.
Change your config file to look something like this:
'gii'=>array(
'class'=>'system.gii.GiiModule',
'password'=>'your_password',
'ipFilters'=>array('192.168.175.1'), //Add your client IP here
),
But I still want to know if it 's possible to control the folders creation.
An other observation: I dont see why gii write to the disk runttime/gii/ControllerCode.php (etc.), as it overrides them as soon as you do preview or generate.
gii will replace the yiic generators, and it offers more (of course). We will add the model generator for sure. The current interfaces are more like translating from the yiic generators. In the future, we may consider adding more customization options (such as specifying the validation rules/attribute types, etc.)
@abajja: those runtime writings are for "sticky attribute" feature. That is, it will remember your last input. For example, if you have multiple sets of code template for the same generator, and you pick up one during this time, then next time when you use the generator again, it will remember the choice you made last time.
gii is meant to be a development tool, while RBAC management is part of application logic. Therefore, we do not want to mix them together.
In future, we may consider providing a skeleton application that has commonly needed features, such as user management, content management, RBAC management, log management, statistics, and so on.