-
Notifications
You must be signed in to change notification settings - Fork 27
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
freephile
wants to merge
351
commits into
enterprisemediawiki:34.x
Choose a base branch
from
freephile:34.x
base: 34.x
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…secret-perms Standardize secret config permissions
Issue getting "yum lockfile is held by another process" msg Ref: - ansible/ansible#57189 - enterprisemediawiki#1165
…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
…31.8.0-release 31.8.0 release
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
…31.8.1-release 31.8.1 release
…push-backup-fix2 Make pushed backups in form *push.sql and use them first; more debug
…backup-fix3 Fix bad variable usage
…meza-perm-fix Fix bad owner/group on /opt/data-meza
…pdate.php Make update.php write to a log
This reverts commit cbeda3a.
… - per Rich Evans
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
Issues
Post-merge actions
Post-merge, the following actions need to be addressed: