• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
What the logic behind config files being classes?

I read your user manual entry here: https://github.com/lonnieezell/CodeIgnit...ration.rst and must say it is very well written.

Allowing the application administrator the ability to add and/or change certain config values I/we have without getting the developer involved certain will need a completely new approach in order to load my "database config layer" and override the config files "fast" certainly will be a challenge.

For example I'll set the "default" when I "ship" the application in the config files.
$config['send email on new user'] = true;
$config['email user on account deactivation'] = true;
$config['allow comments on notes'] = true;

Sometimes this could be 100+ values.

Then the administrator can change these at will without getting me involved just to change the code.

Can you think of a easy way to query and loop over the configs to change these when the application is loaded or do you think this will need to be on a as needed bases (ie 100's of db calls)
Right now it's 1 DB call if it's not cached and 0 if it is.


Messages In This Thread
RE: What the logic behind config files being classes? - by dmyers - 04-21-2016, 07:55 AM

Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  

  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2021 MyBB Group.