You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying with other developers to create a docker image of OJS, and I notice that the config file of OJS (config.inc.php) has a lot of options, which triggers some problems, complexity for the "dockerization" of OJS,
my suggestion : reduce the number of options in this config file to the minimum, a good design is to have a very short config file (8 options, or less), and store the rest of options to the database, by doing this it will allow easier backup/maintenance operations, and also dockerization of OJS about the config file (it will allow us to recreate on the fly the config file with few docker environment variables, when the docker image is launching, instead of using a volume for config.inc.php)
currently for me the vital options for config.inc.php are the credentials for the database (login, password, database driver, database host, database name), and perhaps the base url, the rest of the options could be easily moved to the database in a table "base_settings" for example, and let the admin change these settings present in the database with the administration panel,
Hello,
I am trying with other developers to create a docker image of OJS, and I notice that the config file of OJS (config.inc.php) has a lot of options, which triggers some problems, complexity for the "dockerization" of OJS,
my suggestion : reduce the number of options in this config file to the minimum, a good design is to have a very short config file (8 options, or less), and store the rest of options to the database, by doing this it will allow easier backup/maintenance operations, and also dockerization of OJS about the config file (it will allow us to recreate on the fly the config file with few docker environment variables, when the docker image is launching, instead of using a volume for config.inc.php)
currently for me the vital options for config.inc.php are the credentials for the database (login, password, database driver, database host, database name), and perhaps the base url, the rest of the options could be easily moved to the database in a table "base_settings" for example, and let the admin change these settings present in the database with the administration panel,
check the other CMS like wordpress, they use a very short config file :
https://github.com/WordPress/WordPress/blob/master/wp-config-sample.php
The text was updated successfully, but these errors were encountered: