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
This is the prerequisite for web panel config editor.
MAIN CONFIG FILE: This file will be untouched by the administrator. When doing updates, it will be safe to overwrite everything here.
GLOBAL INSTANCE CONFIG FILE: Defines from the main config file can be copy-pasted & changed on this file, and they will overwrite the values of main config file. Will include stuff like location of mod passwords. Akin to vichan's https://github.com/vichan-devel/vichan/blob/master/inc/instance-config.php
BOARD INSTANCE CONFIG FILE: Will get the values from two files above, and further include database configuration and other possible board-specific configurations (like sensors, if wished to be different on different boards)
BOARD ROOT CONFIG FILE: The reason it's a different file than above is security reasons. Will just link to the board instance config file from the board's root.
I think config files (other than the root one obviously) can just go to dat/ - multi board BBS admins can change locations of config files to be convenient in their systems.
The text was updated successfully, but these errors were encountered:
This is the prerequisite for web panel config editor.
MAIN CONFIG FILE: This file will be untouched by the administrator. When doing updates, it will be safe to overwrite everything here.
GLOBAL INSTANCE CONFIG FILE: Defines from the main config file can be copy-pasted & changed on this file, and they will overwrite the values of main config file. Will include stuff like location of mod passwords. Akin to vichan's https://github.com/vichan-devel/vichan/blob/master/inc/instance-config.php
BOARD INSTANCE CONFIG FILE: Will get the values from two files above, and further include database configuration and other possible board-specific configurations (like sensors, if wished to be different on different boards)
BOARD ROOT CONFIG FILE: The reason it's a different file than above is security reasons. Will just link to the board instance config file from the board's root.
I think config files (other than the root one obviously) can just go to dat/ - multi board BBS admins can change locations of config files to be convenient in their systems.
The text was updated successfully, but these errors were encountered: