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

Merge freephile:34.x into enterprisemediawiki:34.x #1253

Open
wants to merge 351 commits into
base: 34.x
Choose a base branch
from

Conversation

freephile
Copy link
Contributor

Changes

The 34.x branch was based on the enterprisemediawiki:32.x branch. The 34.x branch is still a work in progress, but is close to being ready for use. This brings several enhancements, notably:

  1. MediaWiki REL1_34
  2. updates to all extensions that use that branch
  3. updates to Elasticsearch to 6.x (for new installs) 5.x for existing installs
  4. updates to PHP to 7.2
  5. updates to MariaDB to 10.3.22 (for new installs) ... and MariaDB 10.4 is planned
  6. automatic certificate provisioning using Certbot
  7. pretty URLs
  8. and more

Issues

Post-merge actions

Post-merge, the following actions need to be addressed:

jamesmontalvo3 and others added 30 commits June 4, 2019 06:38
…secret-perms

Standardize secret config permissions
…yum-lock-timeout

Add lock_timeout to yum/package modules to fix Ansible 2.8 issue
…dev-networking

Don't use 'meza' command for dev-networking
my first pull request
changed version from "dev-master" to "2.0.0"
'notify' tag was mixed with 'never' tag, such that it seemed to make
sense to do '--tags notify' to get it to notify. However, this would
then skip over other things not tagged 'notify' like 'uploads' and 'db'.
Instead you'd have to do '--tags db,uploads,anything-else-required'.
Maybe '--tags all,notify' would work, but that's also confusing. Instead
this commit removes the 'never' tag so notification will always happen.
If a user wants to prevent notification they can do '--skip-tags notify'

For some reason the list of servers to exclude on the push-backup
playbook took the 32.x form with server groups like
load-balancers-nonmeza. This missed load-balancers-unmanaged, the 31.x
group naming.
…push-backup-fix

push-backup: Fix bad use of 'notify' tag; Add servers to exclude
…saml-permissions-fix

Fixes for some servers setting zero "others" permissions
…push-backup-fix2

Make pushed backups in form *push.sql and use them first; more debug
…meza-perm-fix

Fix bad owner/group on /opt/data-meza
…pdate.php

Make update.php write to a log
Greg Rundlett and others added 30 commits September 6, 2020 03:13
This reverts commit cbeda3a.
Including XFF header first. Make GoAccess compatible with new format
Changed Apache Main task to include symlinks to log files in the 'Windows' style 'access.log' and 'error.log'
Changed Apache-PHP template for httpd.conf to log to the UNIX standard location of 'access_log'
Changed the LogFormat directive in Apache to use the NCSA Combined format with a prefixed XFF header
Changed the GoAccess log analyzer to be compatible with the new Apache log format.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants