Open freephile opened 4 months ago
Just like Apache is typically configured in a series of 'conf' files, Meza should be too. Meza currently goes through a lot of gymnastics to figure out what wikis exist (by reading the fileystem in the document root) and what aliases might exist (by reading configuration) and it is mostly opaque to the system administrator. Using a declarative approach where wikis, aliases, and attributes of each wiki are defined in a configuration file would bring clarity and simplify the codebase.
A file-based approach would not preclude us from offering wildcard, pattern matching, and default handling (viz Apache Mass Virtual Hosting).
Meza already uses YAML for specifying extensions and skins, so this work would be to follow that same approach.
See too: MediaWiki specifies DB Schema in JSON
Standardize Meza to be like MediaWiki itself: convert Meza to use a declarative wiki ID (e.g. in YAML or JSON) rather than the current indirect method of reading directories in the server document root.