| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| config:cnf_files [2022/03/14 19:21] – [See Also] Andre | config:cnf_files [2023/07/30 13:35] (current) – [Development Notes] typo fixed and more detail added digital man |
|---|
| ====== .cnf files ====== | ====== .cnf files ====== |
| |
| ''.cnf'' files are proprietary binary configuration files located in the ''[[dir:ctrl]]'' directory and ''[[dir:node]]'' directories and are maintained using the [[util:SCFG]] utility. | ''.cnf'' files are proprietary binary configuration files located in the ''[[dir:ctrl]]'' directory and ''[[dir:node]]'' directories and are maintained using the [[util:SCFG]] utility before Synchronet v3.20. |
| |
| ===== Auto-backup ===== | ===== Auto-backup ===== |
| ====== Development Notes ====== | ====== Development Notes ====== |
| |
| These files were originally a text-based configuration but were converted to binary for efficiency reasons which no longer apply. In some future version of Synchronet, these files will be converted to a text format, most likely [[.ini files]]. | These files were originally a text-based configuration (''*.cfg'' files in Synchronet version 1) but were converted to binary for efficiency reasons that no longer apply. In version 3.20 of Synchronet, these files were converted to [[.ini files]]; see [[history:newcfgfiles]] for details. |
| | |
| The multiple ''node.cnf'' files need to be replaced by a single file which configures all the nodes for a specific instance of Synchronet. Currently, this means supporting the ''<base>.<host|os>.<ext>'' format because the assumption that the only reason to run multiple instances is that there are multiple systems is currently baked in. | |
| ===== See Also ===== | ===== See Also ===== |
| * [[:util:SCFG:]] | * [[:util:SCFG:]] |
