Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use a declarative wiki ID (e.g. in JSON) #101

Open
Tracked by #99
freephile opened this issue Apr 26, 2024 · 2 comments
Open
Tracked by #99

Use a declarative wiki ID (e.g. in JSON) #101

freephile opened this issue Apr 26, 2024 · 2 comments
Labels
ansible RedHat Ansible apache web server best practices doing the right stuff code health best practices db Database - MariaDB related DevOps Work on the GitHub system or Deployments doc Improvements or additions to documentation enhancement New feature or request mediawiki MediaWiki related performance fast is good php PHP Hypertext Preprocessor python Python programming yaml yaml ain't markup language

Comments

@freephile
Copy link
Owner

freephile commented Apr 26, 2024

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.

@freephile freephile changed the title Standardize Meza to be like MediaWiki itself: convert Meza to use a declarative wiki ID (e.g. in JSON) rather than the current indirect method of reading directories in the server document root. Use a declarative wiki ID (e.g. in JSON) Apr 26, 2024
@freephile
Copy link
Owner Author

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).

@freephile freephile added doc Improvements or additions to documentation enhancement New feature or request python Python programming ansible RedHat Ansible php PHP Hypertext Preprocessor db Database - MariaDB related mediawiki MediaWiki related code health best practices best practices doing the right stuff performance fast is good apache web server DevOps Work on the GitHub system or Deployments yaml yaml ain't markup language labels Apr 26, 2024
@freephile
Copy link
Owner Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ansible RedHat Ansible apache web server best practices doing the right stuff code health best practices db Database - MariaDB related DevOps Work on the GitHub system or Deployments doc Improvements or additions to documentation enhancement New feature or request mediawiki MediaWiki related performance fast is good php PHP Hypertext Preprocessor python Python programming yaml yaml ain't markup language
Projects
None yet
Development

No branches or pull requests

1 participant