we have been working on a project for a while (i think we used fuelphp since its beta version!) and now the project (web app) is being used on multiple servers and even more local machines (multiple platforms) so suddenly PRODUCTION and DEVELOPMENT environments are not enough, so we started to ignore the config folder from GIT but found out this is even worse and config hell exploded in our faces :(
what is the best way to define more config profiles?
can i use Config::load to load a specific file (absolute path) ?
where is the best location to override and load settings? im trying to do it after Fuel::init in bootstrab
kindly note i dont want to touch the core as this too turned out to be a bad idea when it comes to upgrading and thanks in advance!!
I had a similar approach and I decided to create a module to load the configurations file.
You can insert here your custom configuration and name the configuration file with the site-name and load manually the configuration file in the Base template, if you use this, or in the "before" method of your controller.
thanks ilNotturno however i made a quick hack for now by requiring php files with config::set statements to override settings after Fuel::init call and creating a file just to hold the current profile file name,this way we can add all files to GIT and modify only one variable in one file to select active settings
the main problem was changing the config files for many setups (some are devs and others are production plus testing..) my solution was loading custom configs based on the current url (not very happy about it but its saved us from the pain of updating files by mistake or worse ignoring config files from the GIT repo which was the worst decision ever lol)
Donate
