Currently we have a project hosted in Azure. In oder versions of SEOChecker it seemed like it was writting all settings to the DB. Now this is different, the settings are written to the config: SEOChecker.config. This is giving problems on our Azure subscription, cause App services are not really designed to write or create files. This results to us copying the config before deploy en then overwrite it again after deploy. Is there a way or settings somewhere where I can set it to write to the DB rather than a file. I am sure we are not the 1st with this problem.
It has always been writing settings to the config file. Maybe in a next version this can change. Problem is that I have done something like that for Mediaprotect in the past and that caused issues where people complained that it needed to access the database, chicken/egg problem.
Maybe some sort of switch will help that you can pick where you weant to store the config file.
Having hit this same problem (in our case, the config file from the nuget package being overwritten with every CI deployment), what's the status or suggested workaround here?
Furthermore, when using an Azure load-balancing setup (in the Umbraco recommended configuration, ie with separate apps for frontend and backoffice), the frontends don't ever get config updates made from the backoffice, unless they receive a manual config file deployment and restart.
Even if the config remains in file and not database, it appears SEOChecker doesn't use an ICacheRefresher to distribute config changes?
Thanks Richard - to clarify, settings saved from the backoffice are persisted to the disk config file, and a cache refresh triggers each instance to reload settings, but only if the config file is shared (in a flexible load-balancing setup)?
In our case, and to enable flexible load-balancing in Azure, the backoffice doesn't share the same filesystem.
So database-config is coming in 2.10? The million-dollar question - any timescale on that? ;-)
Development is Scheduled for September. Config location will also be using Umbraco Dependency injection so if you want to put store it on the moon it's also possible :-) This was still a bit legacy from V7 version..
SEOChecker to write to DB instead of config
Currently we have a project hosted in Azure. In oder versions of SEOChecker it seemed like it was writting all settings to the DB. Now this is different, the settings are written to the config: SEOChecker.config. This is giving problems on our Azure subscription, cause App services are not really designed to write or create files. This results to us copying the config before deploy en then overwrite it again after deploy. Is there a way or settings somewhere where I can set it to write to the DB rather than a file. I am sure we are not the 1st with this problem.
Hi,
It has always been writing settings to the config file. Maybe in a next version this can change. Problem is that I have done something like that for Mediaprotect in the past and that caused issues where people complained that it needed to access the database, chicken/egg problem.
Maybe some sort of switch will help that you can pick where you weant to store the config file.
Best,
Richard
Having hit this same problem (in our case, the config file from the nuget package being overwritten with every CI deployment), what's the status or suggested workaround here?
Furthermore, when using an Azure load-balancing setup (in the Umbraco recommended configuration, ie with separate apps for frontend and backoffice), the frontends don't ever get config updates made from the backoffice, unless they receive a manual config file deployment and restart.
Even if the config remains in file and not database, it appears SEOChecker doesn't use an ICacheRefresher to distribute config changes?
Jeavon made https://github.com/Jeavon/SEOCheckerCacheRefresher some time ago, but that would at best clear cached settings, not distribute updated settings.
This is really needed for modern, scalable, Azure-friendly setups.
Hi Phil,
It's on the list for 2.10, It should be using the cache refresher on config changes since it clears the cache the cache uses the method from jeavon.
Best,
Richard
Thanks Richard - to clarify, settings saved from the backoffice are persisted to the disk config file, and a cache refresh triggers each instance to reload settings, but only if the config file is shared (in a flexible load-balancing setup)?
In our case, and to enable flexible load-balancing in Azure, the backoffice doesn't share the same filesystem.
So database-config is coming in 2.10? The million-dollar question - any timescale on that? ;-)
Phil
Development is Scheduled for September. Config location will also be using Umbraco Dependency injection so if you want to put store it on the moon it's also possible :-) This was still a bit legacy from V7 version..
Great to hear, thanks Richard!
is working on a reply...