Announcing Bonfire - A jumpstart for your web apps

[eluser]xmonader[/eluser]
Great project. Thanks for your efforts.

I've checked the Roles module, but ... altering tables/add columns ? <what if i've a large set of permissions>?

RBAC is the way to go? http://en.wikipedia.org/wiki/Role-based_access_control
Yii/Auth component is a really nice implementation if you got the time to check it.

[eluser]Unknown[/eluser]
thank you so much,
yor information really helped me!

[eluser]kilishan[/eluser]
[quote author="xmonader" date="1304603437"]Great project. Thanks for your efforts.

I've checked the Roles module, but ... altering tables/add columns ? <what if i've a large set of permissions>?[/quote]

Maybe not the most elegant solution, and it's not a CMS. Adding columns to the roles table is the same thing you would have to do if you were writing your own admin script. I guess I don't understand the issue here.

RBAC is the way to go? http://en.wikipedia.org/wiki/Role-based_access_control
Yii/Auth component is a really nice implementation if you got the time to check it.

Are you saying it's a good thing or bad thing that RBAC is included? It sounds like you're saying it's a bad thing but then you cite the Wikipedia article that says it's one of the most commonly used methods of access control.

[eluser]xmonader[/eluser]
I like RBAC, but not liking the way used -adding columns/altering tables-
I've rolled my own rbac library: http://ellislab.com/forums/viewthread/188256/

[eluser]kilishan[/eluser]
That's fair. Everyone has their own preferences. Bonfire's target is a single web application. When creating a single application, the need for a module installer or something similar to run the code to insert things into the database for you, when you only need to do it once since you're not installing and uninstalling apps, is very much overkill. In a situation like a CMS where modules will be added at run-time, your library would work great. For Bonfire's target, I think it's overkill and creates unneccessary complexity when adding a row to a datatabase table is such a simple thing.

[eluser]quasiperfect[/eluser]
@kilishan great work

i will try this in the future for now i took a look around and i'm interested in the Events lib
any docs around examples etc ?

[eluser]kilishan[/eluser]
[quote author="quasiperfect" date="1304997221"]@kilishan great work

i will try this in the future for now i took a look around and i'm interested in the Events lib
any docs around examples etc ?[/quote]

In the develop branch on GitHub, the latest docs should go over usage. Let me know if you have any questions.

[eluser]Unknown[/eluser]
@kilishan

Thanks for your hard work, looks good for creating single aps. I look forward to the tutorial which I take will be ready soon.

[eluser]loosetops[/eluser]
I have looked through Bonfire and it is phenomenal. However, I see a few problems down the road regarding maintainability.

I would like to be able to easily update bonfire modules, HMVC and codeigniter separately as the projects move at different paces. As it currently stands the directory structure is slightly different from a typical codeigniter install, it is a directory deeper and system folder renamed to codeigniter. The included HMVC is modified in at least one spot (.../third_party/MX/Modules.php the module locations array). A good spot for that particular change is in the main config.php file as suggested by the HMVC wiki.

As it is now, Bonfire is a single and simple install this means we the users get it easy the first time we use it to start new projects and then things may get slightly complex when updating existing projects. Or when HMVC and codeigniter are updated you would have to update Bonfire even for very small changes.

Somewhere, you mentioned update functionality. That would alleviate my concerns. But, bonfire is saving us weeks of work not just 40 hours; an extra 5 minutes spent by installing CI, HMVC and Bonfire(modules & themes) separately wouldn't make it any less awesome for us.

[eluser]kilishan[/eluser]
@authorfre - Hope you enjoy it. I am getting close to having the tutorial done. Freelance work is keeping me busy, so the development has been slower (but not at all halted!)

@loosetops - I don't know how many times I've read over the HMVC wiki and still missed that I could put that configuration in the main config file. I will definitely make that change. Thanks for pointing it out!

As for upgrades, That's definitely something that I want to address (unless someone beats me to it...) My current plans are for Bonfire core to be able to have a Wordpress-like upgrade tool. This will probably work over FTP, though I'm tempted to make it also work with Git. This wouldn't touch config files, etc.

Bonfire modules you can mostly drop in place, unless there are database changes. That still has to be worked out, but will probably use migrations. Not 100% on that.

As for CodeIgniter upgrades, if they don't cause any issues with the Bonfire (which I believe the 2.0.2 will due to some security changes that I will have to change throughout the app) then you can simply drop the contents of the system folder into the codeigniter folder and be done with it.

And, while small changes in HMVC and CI might be tempting to upgrade, the way that everything is working together currently, I would only do that on a test copy .

Glad you're liking the app and I'd love to hear any other suggestions or comments.