meza
meza copied to clipboard
Setup an enterprise MediaWiki server with simple commands
http://editorconfig.org
Currently it creates backups a bit too often.
This may be more work than expected due to having to tweak several automated tests.
Currently multiple HAProxy servers don't play nice or actually provide HA. This will not allow multiple load balancers.
(but not on failure (an improvement)) Perhaps grep the last line of ansible install for "failures=0" and if found then show living pigeon, else...
basically emulate travis ci without monolith on host. Make it work on more than just CentOS
Currently HAProxy config has: ``` # errorfile 400 /etc/haproxy/errors/400.http # errorfile 403 /etc/haproxy/errors/403.http # errorfile 408 /etc/haproxy/errors/408.http errorfile 500 /etc/haproxy/errors/500.http # errorfile 502 /etc/haproxy/errors/502.http # errorfile 503 /etc/haproxy/errors/503.http # errorfile...
Currently we have the following, which allows specifying `server_type` for custom crons. ```jinja {% if custom_crons is defined %} # # The following jobs are custom definitions from this meza-instance's...
Add [`$wgShowDBErrorBacktrace`](https://www.mediawiki.org/wiki/Manual:$wgShowDBErrorBacktrace) to debug mode. ```php $wgShowDBErrorBacktrace = true; ```
Add [git auto-completion](https://git-scm.com/book/en/v1/Git-Basics-Tips-and-Tricks) to base meza install. Or perhaps it would be better to add it to the `meza setup dev` command, to keep the base installation smaller/faster. Basically this...