Cachet 2.x has the ability to set various settings. These are stored in the database, but then also cached into a configuration file for performance.
I think as a first pass at implementing this, we can skip writing the configs to a file.
Also, I wonder whether we'd benefit from migrating our existing settings to something like spatie/laravel-settings, since most of Cachet's internals will need to read the settings at various points of the lifecycle.
We're also going to add additional settings such as:
Cachet 2.x has the ability to set various settings. These are stored in the database, but then also cached into a configuration file for performance.
I think as a first pass at implementing this, we can skip writing the configs to a file.
Also, I wonder whether we'd benefit from migrating our existing settings to something like
spatie/laravel-settings
, since most of Cachet's internals will need to read the settings at various points of the lifecycle.We're also going to add additional settings such as: