Le Vendredi 25 Novembre 2005 19:28, dombre a écrit : > Olivier Thauvin a écrit : > >The current code of glpi use backups/dump, glpi/config and docs/ to store > >users data and configuration, needing write access to web server. > > > >Most vendor (unix distribution like Mandriva, Debian or other) prefer to > > split code and static data (read only) from users configuration: > >- for securitty reason, it is not safe to have write access on the http > > tree - convenience purpose, aka make easy backup and update. > > > >User's data are mostly hardcoded into glpi scripts in many location. A > >solution would be to have $cfg_install[...] variable for current > > glpi/config, backups/dump and docs/ into a glpi/config/config_path.php, > > and so using this small script into all other scripts > > (glpi/config/config.php, install.php, etc...). > > > >Using such of > > > >WDYT ? Should I start to make a patch or should I deal with the current > >settings ? > > Hi, > > you could make a patch but using the latest CVS version in order to be > easy to include.
Yes of course. What I was doing. > If you do it all paths must to be configurable online. Sorry ? I have a big doubt. I am talking about the main configuration, aka low level configuration saying where is the rest of configuration. If the interface have to write into this file, we back to problem, aka having to set writting permission somewhere into code tree... This basic setting are dedicate to sys admin, distribution vendor to adapt the soft to their and provide compliance about the rest of software. I assume the packager or the sys admin is able to edit a file to add one or two line. Moreover, my patch will include a basic and commented file as example. The rest of the configuration, aka DB settings, user customization, I agree.
pgp8GvhpC3acp.pgp
Description: PGP signature
