search

mneuhaus / Famelo.Features

3 stars 2 forks source link

Make features manageable via GUI/CLI #1

Open andreaswolf opened 11 years ago

andreaswolf commented 11 years ago

Sometimes, a feature should be enabled for everybody after a short testing period, or some feature is only for a few special customers (the list of which might grow over time). Therefore, it would be nice to have a possibility of dynamically enabling features. This could work the same way the current features configuration works, just not hard-coded in the configuration files but dynamically read from the database. This would especially be interesting for the userPercentage() and hasRole/isUser() matchers.

mneuhaus commented 11 years ago

i kinda did have that before the refactoring. i'm not sure if i want the settings to be in yaml + db. maybe it might make sense to have a gui to alter the root/Configuration/Features.yaml ? What do you think?

andreaswolf commented 11 years ago

I'd rather not have the Configuration files writable by the application (and they're not in my configuration, for security reasons). Probably it does not have to be in the database, but that's the easiest solution for now.

mneuhaus commented 11 years ago

i can understand that. not really that keen on creating a whole gui for this currently to be honest. i could do it quite quickly with expose as i had before, but that would drag expose + typoscript as an dependency into the mix