We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Staging - Mysql 5.7.27, PHP 7.1.30, Apache 2.4.18 Production - Mysql 5.7.27, PHP 7.1.30, Apache 2.4.18
As of 18th June 2019
As apt update gets stale quite quickly, moving forward we will update/upgrade staging, test then immediately update/upgrade live.
The text was updated successfully, but these errors were encountered:
Staging - Mysql 5.7.25, PHP 7.1.20 Production - Mysql 5.7.23, PHP 7.1.17
Update Production to Staging versions (mysql 5.7.25), update staging to latest (5.7.25) - 12th March 2019
Updated Staging PHP7.1 to latest (7.1.27)
Tuesday 7th May
@georgemillard I will find out how to freeze the update so we can upgrade to the version we are testing on staging.
Tuesday 21st May
Sorry, something went wrong.
lettie16
georgemillard
No branches or pull requests
Staging - Mysql 5.7.27, PHP 7.1.30, Apache 2.4.18
Production - Mysql 5.7.27, PHP 7.1.30, Apache 2.4.18
As of 18th June 2019
As apt update gets stale quite quickly, moving forward we will update/upgrade staging, test then immediately update/upgrade live.
The text was updated successfully, but these errors were encountered: