Plugins configuration files not stored in /etc
Plugins configuration files not stored in /etc
The plguins configuration files are currently stored into the /var/cache directory.
This directory is normally reserved to data which are cached and not persistent. So, It's clearly not the right place for storing configuration files.
All the conffiles should be centralized into the /etc/fusiondirectory/ directory.
(from redmine: issue id 1085, created on 2012-06-18, closed on 2013-02-19)
- Changesets:
- Revision f197b077 by Benoit MORTIER on 2012-11-21T12:22:32.000Z:
Fixes: #1085 Plugins configuration files not stored in /etc- Revision da023253 by Côme Chilliet on 2013-01-16T15:13:55.000Z:
Fixes: #1085 Plugins configuration files should be in LDAP- Revision 6e48b269 by Côme Chilliet on 2013-01-16T15:14:15.000Z:
Fixes: #1085 Removed shells file- Revision 1e5fd8c3 by Benoit MORTIER on 2013-02-01T09:44:02.000Z:
Fixes: #1085 Plugins configuration files not stored in /etc- Custom Fields:
- Bug in version: 1.0.4
- Uploads:
Activity
Hello,
i made this change to allow fusiondirectory to be installed on vps and shared hosting where people don't have access to /etc, and i think its better to have only one place where you can find everything, maybe we should choose another dir for the plugins text files
Cheers
(from redmine: written on 2012-06-30)
By bmortier on 2017-09-02T14:45:55 (imported from GitLab)
About the VPS / shared hosting : I don't think that installing FD on such a target is relevant. I think that people who install FD are sysadmin and that they have all the ressources to install FD properly on a server. We should focus on this case and not on the shared hosting case which I think don't represent a case which deserves a specific management.
By the way, if we consider the case, what about the config files already deployed in /etc like fusiondirectory.conf and fusiondirectory.secrets ?
I still think that for all the configuration files, we must be standard and store them in the correct configuration directory (/etc for Linux and /usr/local/etc for *BSD families). /etc is the correct and the most known place for configuration files so we shouldn't change that.
Moreover if we do that, we will risk to have difficulties to integrate distributions which want to have configuration files in the configuration directory.
(from redmine: written on 2012-07-04)
By obonhomme on 2017-09-02T14:45:56 (imported from GitLab)
Hello,
now that we started to have a ldap config backend, i think all those file should be replaced by a config tab in the plugin allowing to edit those properties and having default values
Cheers
(from redmine: written on 2012-11-13)
By bmortier on 2017-09-02T14:45:56 (imported from GitLab)
Hello, This patch adds a tab to the config screen which will be used for small plugin configuration. (For instance all plugins that only have one RDN to define) I added ogroupRDN in this tab so that it's not empty. roleRDN, aliasRDN, etc… are gonna be stored here.
(from redmine: written on 2012-11-21)
By Côme Chilliet on 2017-09-02T14:45:57 (imported from GitLab)
/!\ This removes ldif files from contrib/openldap This patch also adds the shells to the config screen, instead of having them in the /var/cache folder. Multi-valuated settings are now returned as an array by config class.
(from redmine: written on 2013-01-16)
By Côme Chilliet on 2017-09-02T14:45:57 (imported from GitLab)
