-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate conf_2_db feature #1424
Comments
Sounds good to me 👍 |
I precisely just used it for color settings. :-) It is useful when, like I do, you regularly import new robots, when people are migrating from self hosting to a shared server. I remember why the conf_2_db feature had been asked: It was for people running a very large number of virtual hosts (I'm speaking thousands of robots). When reloading Sympa processes, reading the config files seemed to be a problem. I don't know why it was not applied to all Sympa daemons. Just a history note so you get some context. Anyway, while running this command, I noticed a few bugs (introduced a long time ago). Is it still useful that I propose the fixes? |
OK. It turns out that this is one of the features that was only planned but not working properly. In these years, I have been working on fixing many of those things to make them really usable or removing them to cleanup code. I am happy to be able to safely remove this (unfinished) feature since it has never been used (except for color settings) in the first place. |
Yes that makes sense to me. |
Expected Behavior
The feature to save configuration into database table should be deprecated.
Current Behavior
There are two use cases:
Content of
sympa.conf
and/orrobot.conf
may be imported intoconf_table
in database withsympa.pl --conf_2_db
, and they may override default values of configuration.However, configuration in database affects only
sympa_msg.pl
andsympa_automatic.pl
daemons andsympa.pl
command line utility. The other daemons and most of command line tools seem not affected.Color setting (
color_*
parameters) on web UI are saved intoconf_table
, and they override configuration in eachrobot.conf
.These settings are shared by possible multiple FastCGI servers through the database.
Possible Solution
conf_2_db
feature to import configuration into database table.The setting imported into database should be exported to the configuration files during upgrade process.[EDIT] It turned out that this feature has not dealt with the parameters other than CSS colors, so exporting parameters to the configuration files is unnecessary.
Context
This feature was introduced in Sympa 6.1. cf. the initial commit.
Probably it has been rarely used, except for color settings.
Deprecating this, configuration will be independent from database. It will make the code simpler.
The text was updated successfully, but these errors were encountered: