Replies: 2 comments 5 replies
-
Safest solutionPublish all internal config files.
Dangerous solutionIf there is a config cache, internal config will not be read. |
Beta Was this translation helpful? Give feedback.
2 replies
-
There should definitely be a way to do this. The config files having all sorts of stuff we don't want is not helpful. Database config for example should never have connections that don't exist. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
#47309 forces now everyone to live with base configs merged in your configs with the introduction of
\Illuminate\Foundation\Bootstrap\LoadConfiguration::getBaseConfiguration
and the logic inloadConfigurationFile()
andmergeableOptions()
.I understand how and why, but in my case I want full control, as I have with < Laravel 11, what is in the config and what not. It becomes risky to perform updates if updates to base configs are made and defaults might change and you might not find out before production due to different environments etc.
TL;DR: is there an easy way to disable this behaviour without replacing
LoadConfiguration
bootstrapper?Beta Was this translation helpful? Give feedback.
All reactions