We now support MoinMoin Wiki 1.9.11.

We will be updating all Managed MoinMoin Wiki Hosting accounts this week following our usual four-round release cycle, with development sites being updated today (Tuesday).

Please thoroughly test your development sites early before updates make it to production update rounds on Thursday and Friday.

As usual, we will perform these updates during your scheduled maintenance times.

We have upgraded our jdk-lts meta-package from Java 8 (LTS) to Java 11 (LTS).

We have added a new jdk-old meta-package that remains Java 8 (LTS).

Please review the following migration guides for this upgrade:

1. Java 11 Migration Guide

For managed servers, we have replaced all /opt/jdk-lts/profile.* with /opt/jdk-old/profile.*, so applications will not be upgraded to a new major version unannounced. For each of the applications now on /opt/jdk-old/profile.*, we have communicated with clients requesting permission to upgrade to Java 11.

We also replaced all /opt/jdk-11/profile.* with /opt/jdk-lts/profile.*. We had already worked with clients to move most applications to Java 11, so this change is consistent with the intent of the existing Java 11 applications.

For our Remote Desktops, we have replaced the antiquated VNC Java Applet with the much more modern and compatible JavaScript-only noVNC. While noVNC connects over WebSockets, custom clients may still connect to port 5900/TCP with SSL enabled.

CentOS 7 kernel 3.10.0-1160.11.1 is now available. Please see RedHat Security Advisory 2020:5437 for more details.

This update does include fixes for remote exploits, so we are updating all managed servers.

As usual, we will perform these updates during your scheduled maintenance times while performing any documented per-server custom procedures before and after the reboot.

Tomcat 7.0 will be end-of-life on 2021-03-31 per End of life for Apache Tomcat 7.0.x.

The following versions of Tomcat will be supported at the time Tomcat 7.0 becomes end-of-life:

1. Tomcat 8.5
2. Tomcat 9.0
3. Tomcat 10.0

Please review the following migration guides in preparation for this upgrade:

1. Tomcat 8.5.x Migration Guide
2. Tomcat 9.0.x Migration Guide
3. Tomcat 10.0.x Migration Guide

We will communicate with you individually to coordinate any required upgrades before Tomcat 7.0 reaches end-of-life.

Once end-of-life is reached, we will upgrade any remaining uses of Tomcat 7.0 to Tomcat 8.5.

We will carefully review all server.xml and web.xml files to maintain any customizations through the upgrade. As usual, we will perform these updates during your scheduled maintenance times.

Java 15 will be end-of-life in March 2021 per Oracle Java SE Support Roadmap.

Please review the following resources in preparation for this upgrade:

1. JDK 16

Once end-of-life is reached:

1. Applications that use /opt/jdk-current/profile.* will switch from Java 15 to Java 16 on their next restart.
2. For all managed servers, we will replace /opt/jdk-15/profile.* with /opt/jdk-16/profile.*. We will also restart all applications currently running Java 15, so their profile scripts can select a newer version of Java.

As usual, we will perform these updates during your scheduled maintenance times.

PHP 7.3 will be end-of-life on 2021-12-06 per PHP: Supported Versions.

The following versions of PHP will be supported at the time PHP 7.3 becomes end-of-life:

1. PHP 5.4 (CentOS 7)
2. PHP 7.4
3. PHP 8.0

Please review the following migration guides in preparation for this upgrade:

1. Migrating from PHP 7.3.x to PHP 7.4.x
2. Migrating from PHP 7.4.x to PHP 8.0.x

We will communicate with you individually to coordinate any required upgrades before PHP 7.3 reaches end-of-life.

Once end-of-life is reached, we will upgrade any remaining uses of PHP 7.3 to PHP 7.4.

We will carefully review all php.ini files to maintain any customizations through the upgrade. As usual, we will perform these updates during your scheduled maintenance times.

We now support Python 3.9.

Python 3.9 may be used for any existing user or application by updating your profile script to include /opt/python-3.9/profile.sh (for Bourne shells) or /opt/python-3.9/profile.csh (for C shells).

The 3.9.0 build is without --enable-optimizations due to "Could not import runpy module". This had also happened on the initial releases of the 3.7 series. If this issue persists, we will look into building with a newer version of GCC, instead of the aging version of GCC that comes with CentOS 7.

We are updating all managed servers from CentOS 7.8.2003 to CentOS 7.9.2009 this week.

We have not experienced any compatibility issues during our packaging and testing. However, the following guides may assist you in evaluating compatibility:

• CentOS 7.9 Release Notes
• Red Hat Enterprise Linux 7.9 Release Notes

This update includes an updated kernel, so each server will be rebooted as part of the update process. As usual, we will perform these updates during your scheduled maintenance times while performing any documented per-server custom procedures before and after the reboot.

We now support Java 15.

Java 15 may be used for any existing application by updating your profile script to include /opt/jdk-15/profile.sh (for Bourne shells) or /opt/jdk-15/profile.csh (for C shells). See this FAQ for more details on how to change Java versions:

/clientarea/FAQ.ao?category=jvms&page=profile

As this is a non-LTS version, Java 15 will be supported until Java 16 is available. At that time, all uses of Java 15 will be automatically updated to Java 16.

PostgreSQL 9.5 will be end-of-life on 2021-02-11 per PostgreSQL: Versioning Policy.

The following versions of PostgreSQL will be supported at the time PostgreSQL 9.5 becomes end-of-life:

1. PostgreSQL 9.6
2. PostgreSQL 10
3. PostgreSQL 11
4. PostgreSQL 12
5. PostgreSQL 13

We will communicate with you individually to coordinate any required upgrades before PostgreSQL 9.5 reaches end-of-life.

Once end-of-life is reached, we will upgrade any remaining uses of PostgreSQL 9.5 to PostgreSQL 9.6.

As usual, we will perform these updates during your scheduled maintenance times.

PHP 7.2 will be end-of-life on 2020-11-30 per PHP: Supported Versions.

The following versions of PHP will be supported at the time PHP 7.2 becomes end-of-life:

1. PHP 5.4 (CentOS 7)
2. PHP 7.3
3. PHP 7.4
4. PHP 8.0

Please review the following migration guides in preparation for this upgrade:

1. Migrating from PHP 7.2.x to PHP 7.3.x
2. Migrating from PHP 7.3.x to PHP 7.4.x
3. Migrating from PHP 7.4.x to PHP 8.0.x

We will communicate with you individually to coordinate any required upgrades before PHP 7.2 reaches end-of-life.

Once end-of-life is reached, we will upgrade any remaining uses of PHP 7.2 to PHP 7.3.

We will carefully review all php.ini files to maintain any customizations through the upgrade. As usual, we will perform these updates during your scheduled maintenance times.

Python 3.5 is now end-of-life.

The following versions of Python are currently supported:

1. Python 3.6
2. Python 3.7
3. Python 3.8

For all managed servers, we are upgrading any remaining uses of Python 3.5 to Python 3.6.

As usual, we will perform these updates during your scheduled maintenance times.

We now support WordPress 5.5 “Eckstine”.

We will be updating all Managed WordPress Hosting accounts this week following our usual four-round release cycle, with development sites being updated today (Tuesday).

Please thoroughly test your development sites early before updates make it to production update rounds on Thursday and Friday.

As usual, we will perform these updates during your scheduled maintenance times.

Python 3.5 will be end-of-life on 2020-09-13 per Status of Python branches.

The following versions of Python will be supported at the time Python 3.5 becomes end-of-life:

1. Python 3.6
2. Python 3.7
3. Python 3.8

We will communicate with you individually to coordinate any required upgrades before Python 3.5 reaches end-of-life.

Once end-of-life is reached, we will upgrade any remaining uses of Python 3.5 to Python 3.6.

As usual, we will perform these updates during your scheduled maintenance times.

MySQL 5.6 will be end-of-life February 2021 per Oracle Lifetime Support Policy for Technology Products Guide.

The following versions of MySQL will be supported at the time MySQL 5.6 becomes end-of-life:

1. MySQL 5.7
2. MySQL 8.0

Please review the following migration guides in preparation for this upgrade:

1. Changes in MySQL 5.7
2. Changes in MySQL 8.0

We will communicate with you individually to coordinate any required upgrades before MySQL 5.6 reaches end-of-life.

Once end-of-life is reached, we will upgrade any remaining uses of MySQL 5.6 to MySQL 5.7.

As usual, we will perform these updates during your scheduled maintenance times.

Java 14 will be end-of-life in September 2020 per Oracle Java SE Support Roadmap.

Please review the following resources in preparation for this upgrade:

1. JDK 15

Once end-of-life is reached:

1. Applications that use /opt/jdk-current/profile.* will switch from Java 14 to Java 15 on their next restart.
2. For all managed servers, we will replace /opt/jdk-14/profile.* with /opt/jdk-15/profile.*. We will also restart all applications currently running Java 14, so their profile scripts can select a newer version of Java.

As usual, we will perform these updates during your scheduled maintenance times.

We now support WordPress 5.4.2.

We will be updating all Managed WordPress Hosting accounts this week following our usual four-round release cycle, with development sites being updated today (Tuesday).

Please thoroughly test your development sites early before updates make it to production update rounds on Thursday and Friday.

As usual, we will perform these updates during your scheduled maintenance times.

PHP 7.2 will be end-of-life on 2020-11-30 per PHP: Supported Versions.

The following versions of PHP will be supported at the time PHP 7.2 becomes end-of-life:

1. PHP 5.4 (CentOS 7)
2. PHP 7.3
3. PHP 7.4
4. PHP 8.0

Please review the following migration guides in preparation for this upgrade:

1. Migrating from PHP 7.2.x to PHP 7.3.x
2. Migrating from PHP 7.3.x to PHP 7.4.x
3. Migrating from PHP 7.4.x to PHP 8.0.x

We will communicate with you individually to coordinate any required upgrades before PHP 7.2 reaches end-of-life.

Once end-of-life is reached, we will upgrade any remaining uses of PHP 7.2 to PHP 7.3.

We will carefully review all php.ini files to maintain any customizations through the upgrade. As usual, we will perform these updates during your scheduled maintenance times.

Java 7 (LTS) will be end-of-life in June 2020 per OpenJDK Lifecycle Dates and RHEL versions.

The following versions of Java will be supported at the time Java 7 (LTS) becomes end-of-life:

1. Java 8 (LTS)
2. Java 11 (LTS)
3. Java 15

Please review the following migration guides in preparation for this upgrade:

1. Java 8 Adoption Guide
2. Java 11 Migration Guide
3. Java 12 Migration Guide
4. Java 13 Migration Guide
5. Java 14 Migration Guide
6. Java 15 Migration Guide

We will communicate with you individually to coordinate any required upgrades before Java 7 (LTS) reaches end-of-life.

Once end-of-life is reached:

1. Applications that use /opt/jdk-oldlts/profile.* will switch from Java 7 to Java 8 on their next restart.
2. For all managed servers, we will replace /opt/jdk-7/profile.* with /opt/jdk-8/profile.*. We will also restart all applications currently running Java 7, so their profile scripts can select a newer version of Java.

As usual, we will perform these updates during your scheduled maintenance times.

We are updating all managed servers from CentOS 7.7.1908 to CentOS 7.8.2003 this week.

We have not experienced any compatibility issues during our packaging and testing. However, the following guides may assist you in evaluating compatibility:

• CentOS 7.8 Release Notes
• Red Hat Enterprise Linux 7.8 Release Notes

This update includes an updated kernel, so each server will be rebooted as part of the update process. As usual, we will perform these updates during your scheduled maintenance times while performing any documented per-server custom procedures before and after the reboot.

Tomcat 7.0 will be end-of-life on 2021-03-31 per End of life for Apache Tomcat 7.0.x.

The following versions of Tomcat will be supported at the time Tomcat 7.0 becomes end-of-life:

1. Tomcat 8.5
2. Tomcat 9.0
3. Tomcat 10.0

Please review the following migration guides in preparation for this upgrade:

1. Tomcat 8.5.x Migration Guide
2. Tomcat 9.0.x Migration Guide
3. Tomcat 10.0.x Migration Guide

We will communicate with you individually to coordinate any required upgrades before Tomcat 7.0 reaches end-of-life.

Once end-of-life is reached, we will upgrade any remaining uses of Tomcat 7.0 to Tomcat 8.5.

We will carefully review all server.xml and web.xml files to maintain any customizations through the upgrade. As usual, we will perform these updates during your scheduled maintenance times.

We now support Java 14.

Java 14 may be used for any existing application by updating your profile script to include /opt/jdk-14/profile.sh (for Bourne shells) or /opt/jdk-14/profile.csh (for C shells). See this FAQ for more details on how to change Java versions:

/clientarea/FAQ.ao?category=jvms&page=profile

As this is a non-LTS version, Java 14 will be supported until Java 15 is available. At that time, all uses of Java 14 will be automatically updated to Java 15.

Java 7 (LTS) will be end-of-life in June 2020 per OpenJDK Lifecycle Dates and RHEL versions.

The following versions of Java will be supported at the time Java 7 (LTS) becomes end-of-life:

1. Java 8 (LTS)
2. Java 11 (LTS)
3. Java 15

Please review the following migration guides in preparation for this upgrade:

1. Java 8 Adoption Guide
2. Java 11 Migration Guide
3. Java 12 Migration Guide
4. Java 13 Migration Guide
5. Java 14 Migration Guide
6. Java 15 Migration Guide

We will communicate with you individually to coordinate any required upgrades before Java 7 (LTS) reaches end-of-life.

Once end-of-life is reached:

1. Applications that use /opt/jdk-oldlts/profile.* will switch from Java 7 to Java 8 on their next restart.
2. For all managed servers, we will replace /opt/jdk-7/profile.* with /opt/jdk-8/profile.*. We will also restart all applications currently running Java 7, so their profile scripts can select a newer version of Java.

As usual, we will perform these updates during your scheduled maintenance times.

Java 13 will be end-of-life in March 2020 per Oracle Java SE Support Roadmap.

Please review the following resources in preparation for this upgrade:

1. JDK 14

Once end-of-life is reached:

1. Applications that use /opt/jdk-current/profile.* will switch from Java 13 to Java 14 on their next restart.
2. For all managed servers, we will replace /opt/jdk-13/profile.* with /opt/jdk-14/profile.*. We will also restart all applications currently running Java 13, so their profile scripts can select a newer version of Java.

As usual, we will perform these updates during your scheduled maintenance times.

PostgreSQL 9.5 will be end-of-life on 2021-02-11 per PostgreSQL: Versioning Policy.

The following versions of PostgreSQL will be supported at the time PostgreSQL 9.5 becomes end-of-life:

1. PostgreSQL 9.6
2. PostgreSQL 10
3. PostgreSQL 11
4. PostgreSQL 12
5. PostgreSQL 13

We will communicate with you individually to coordinate any required upgrades before PostgreSQL 9.5 reaches end-of-life.

Once end-of-life is reached, we will upgrade any remaining uses of PostgreSQL 9.5 to PostgreSQL 9.6.

As usual, we will perform these updates during your scheduled maintenance times.

MySQL 5.6 will be end-of-life February 2021 per Oracle Lifetime Support Policy for Technology Products Guide.

The following versions of MySQL will be supported at the time MySQL 5.6 becomes end-of-life:

1. MySQL 5.7
2. MySQL 8.0

Please review the following migration guides in preparation for this upgrade:

1. Changes in MySQL 5.7
2. Changes in MySQL 8.0

We will communicate with you individually to coordinate any required upgrades before MySQL 5.6 reaches end-of-life.

Once end-of-life is reached, we will upgrade any remaining uses of MySQL 5.6 to MySQL 5.7.

As usual, we will perform these updates during your scheduled maintenance times.

PostgreSQL 9.4 will be end-of-life on 2020-02-13 per PostgreSQL: Versioning Policy.

The following versions of PostgreSQL will be supported at the time PostgreSQL 9.4 becomes end-of-life:

1. PostgreSQL 9.5
2. PostgreSQL 9.6
3. PostgreSQL 10
4. PostgreSQL 11
5. PostgreSQL 12

We will communicate with you individually to coordinate any required upgrades before PostgreSQL 9.4 reaches end-of-life.

Once end-of-life is reached, we will upgrade any remaining uses of PostgreSQL 9.4 to PostgreSQL 9.5.

As usual, we will perform these updates during your scheduled maintenance times.

Java 13 will be end-of-life in March 2020 per Oracle Java SE Support Roadmap.

Please review the following resources in preparation for this upgrade:

1. JDK 14

Once end-of-life is reached:

1. Applications that use /opt/jdk-current/profile.* will switch from Java 13 to Java 14 on their next restart.
2. For all managed servers, we will replace /opt/jdk-13/profile.* with /opt/jdk-14/profile.*. We will also restart all applications currently running Java 13, so their profile scripts can select a newer version of Java.

As usual, we will perform these updates during your scheduled maintenance times.

CentOS 7 kernel 3.10.0-1062.7.1 is now available. Please see RedHat Security Advisory 2019:3979 for more details.

Although this update does not contain any fixes for remote exploits, we will be updating all managed servers as we migrate servers for underlying virtualization platform updates.

As usual, we will perform these updates during your scheduled maintenance times while performing any documented per-server custom procedures before and after the reboot.

PHP 7.1 is now end-of-life.

The following versions of PHP are currently supported:

1. PHP 5.4 (CentOS 7)
2. PHP 7.2
3. PHP 7.3
4. PHP 7.4

Please review the following migration guides for this upgrade:

1. Migrating from PHP 7.1.x to PHP 7.2.x
2. Migrating from PHP 7.2.x to PHP 7.3.x
3. Migrating from PHP 7.3.x to PHP 7.4.x

For all managed servers, we are upgrading any remaining uses of PHP 7.1 to PHP 7.2.

We will carefully review all php.ini files to maintain any customizations through the upgrade. As usual, we will perform these updates during your scheduled maintenance times.

PHP 7.2 will be end-of-life on 2020-11-30 per PHP: Supported Versions.

The following versions of PHP will be supported at the time PHP 7.2 becomes end-of-life:

1. PHP 5.4 (CentOS 7)
2. PHP 7.3
3. PHP 7.4
4. PHP 8.0

Please review the following migration guides in preparation for this upgrade:

1. Migrating from PHP 7.2.x to PHP 7.3.x
2. Migrating from PHP 7.3.x to PHP 7.4.x
3. Migrating from PHP 7.4.x to PHP 8.0.x

We will communicate with you individually to coordinate any required upgrades before PHP 7.2 reaches end-of-life.

Once end-of-life is reached, we will upgrade any remaining uses of PHP 7.2 to PHP 7.3.

We will carefully review all php.ini files to maintain any customizations through the upgrade. As usual, we will perform these updates during your scheduled maintenance times.

We now support PostgreSQL 12. We have included the following modules in our build:

1. cube - Used by the earthdistance module.
2. earthdistance - Allows spatial indexing of geographical coordinates - (latitude, longitude) pairs.

PostgreSQL 9.4 will be end-of-life on 2020-02-13 per PostgreSQL: Versioning Policy.

The following versions of PostgreSQL will be supported at the time PostgreSQL 9.4 becomes end-of-life:

1. PostgreSQL 9.5
2. PostgreSQL 9.6
3. PostgreSQL 10
4. PostgreSQL 11
5. PostgreSQL 12

We will communicate with you individually to coordinate any required upgrades before PostgreSQL 9.4 reaches end-of-life.

Once end-of-life is reached, we will upgrade any remaining uses of PostgreSQL 9.4 to PostgreSQL 9.5.

As usual, we will perform these updates during your scheduled maintenance times.

CentOS 7 kernel 3.10.0-1062.4.1 is now available. Please see RedHat Security Advisory 2019:3055 for more details.

As this update does not include any fixes for remote exploits, we are only updating managed servers with less trusted local users. As most of our clients only have more trusted users within their virtual servers, this means we will only reboot a small minority of the servers we manage.

As usual, we will perform these updates during your scheduled maintenance times while performing any documented per-server custom procedures before and after the reboot.

We now support WordPress 5.2.4.

We will be updating all Managed WordPress Hosting accounts this week following our usual four-round release cycle, with development sites being updated today (Tuesday).

Please thoroughly test your development sites early before updates make it to production update rounds on Thursday and Friday.

As usual, we will perform these updates during your scheduled maintenance times.

Java 12 is now end-of-life.

Please review the following migration guides for this upgrade:

1. Java 13 Migration Guide

Any uses of /opt/jdk-12/profile.* must be updated to either /opt/jdk-lts/profile.* or /opt/jdk-current/profile.* (or a specific newer version), depending on your choice of stability versus features.

Applications that use /opt/jdk-current/profile.* will switch from Java 12 to Java 13 on their next restart.

For all managed servers, we are replacing /opt/jdk-12/profile.* with /opt/jdk-13/profile.*. We are also restarting all applications currently running Java 12, so their profile scripts can select a newer version of Java.

As usual, we will perform these updates during your scheduled maintenance times.

We are updating all managed servers from CentOS 7.6 to CentOS 7.7 this week.

We have not experienced any compatibility issues during our packaging and testing. However, the following guides may assist you in evaluating compatibility:

• CentOS 7.7 Release Notes
• Red Hat Enterprise Linux 7.7 Release Notes

This update includes an updated kernel, so each server will be rebooted as part of the update process. As usual, we will perform these updates during your scheduled maintenance times while performing any documented per-server custom procedures before and after the reboot.

We now support WordPress 5.2.3.

We will be updating all Managed WordPress Hosting accounts this week following our usual four-round release cycle, with development sites being updated today (Tuesday).

Please thoroughly test your development sites early before updates make it to production update rounds on Thursday and Friday.

As usual, we will perform these updates during your scheduled maintenance times.

Java 12 will be end-of-life in September 2019 per Oracle Java SE Support Roadmap.

Please review the following resources in preparation for this upgrade:

1. JDK 13

Once end-of-life is reached:

1. Applications that use /opt/jdk-current/profile.* will switch from Java 12 to Java 13 on their next restart.
2. For all managed servers, we will replace /opt/jdk-12/profile.* with /opt/jdk-13/profile.*. We will also restart all applications currently running Java 12, so their profile scripts can select a newer version of Java.

As usual, we will perform these updates during your scheduled maintenance times.

CentOS 7 kernel 3.10.0-957.27.2 is now available. Please see RedHat Security Advisory 2019:1873 for more details.

As this update does not include any fixes for remote exploits, we are only updating managed servers with less trusted local users. As most of our clients only have more trusted users within their virtual servers, this means we will only reboot a small minority of the servers we manage.

As usual, we will perform these updates during your scheduled maintenance times while performing any documented per-server custom procedures before and after the reboot.

CentOS 7 kernel 3.10.0-957.21.3 is now available. Please see RedHat Security Advisory 2019:1481 for more details.

This update does include fixes for remote exploits, so we are updating all managed servers.

As usual, we will perform these updates during your scheduled maintenance times while performing any documented per-server custom procedures before and after the reboot.

Java 12 will be end-of-life in September 2019 per Oracle Java SE Support Roadmap.

Please review the following resources in preparation for this upgrade:

1. JDK 13

Once end-of-life is reached:

1. Applications that use /opt/jdk-current/profile.* will switch from Java 12 to Java 13 on their next restart.
2. For all managed servers, we will replace /opt/jdk-12/profile.* with /opt/jdk-13/profile.*. We will also restart all applications currently running Java 12, so their profile scripts can select a newer version of Java.

As usual, we will perform these updates during your scheduled maintenance times.

PHP 7.1 will be end-of-life on 2019-12-01 per PHP: Supported Versions.

The following versions of PHP will be supported at the time PHP 7.1 becomes end-of-life:

1. PHP 5.4 (CentOS 7)
2. PHP 7.2
3. PHP 7.3
4. PHP 7.4

Please review the following migration guides in preparation for this upgrade:

1. Migrating from PHP 7.1.x to PHP 7.2.x
2. Migrating from PHP 7.2.x to PHP 7.3.x
3. Migrating from PHP 7.3.x to PHP 7.4.x

We will communicate with you individually to coordinate any required upgrades before PHP 7.1 reaches end-of-life.

Once end-of-life is reached, we will upgrade any remaining uses of PHP 7.1 to PHP 7.2.

We will carefully review all php.ini files to maintain any customizations through the upgrade. As usual, we will perform these updates during your scheduled maintenance times.

CentOS 7 kernel 3.10.0-957.12.2 is now available. Please see RedHat Security Advisory 2019:1168 for more details.

As this update does not include any fixes for remote exploits, we are only updating managed servers with less trusted local users. As most of our clients only have more trusted users within their virtual servers, this means we will only reboot a small minority of the servers we manage.

As usual, we will perform these updates during your scheduled maintenance times while performing any documented per-server custom procedures before and after the reboot.

For Long-Term Support (LTS) versions of Java, we have switched from Oracle's release of OpenJDK to RedHat's releases of OpenJDK (via CentOS).

Oracle does not support the full LTS lifecycle for OpenJDK, whereas RedHat does.

We will continue to use the Oracle OpenJDK for non-LTS versions of Java.

With this change, we have also restored our support of Java 7 (LTS) through its scheduled end-of-life in June 2020.

We have maintained compatibility with existing profile scripts in /opt/jdk-*/profile.sh (for Bourne shells) or /opt/jdk-*/profile.csh (for C shells). The primary difference is the scripts will pick-up the JVM from /usr/lib/jvm/java-*-openjdk-*/ instead of /opt/jdk-*/, but this should be transparent to applications.

For managed servers, we continue to install newer Java releases, work with clients to restart all applications on their schedule, then remove old Java releases once they are no longer used. We never remove a Java release out from under a running application.

We now support Java 12.

Java 12 may be used for any existing application by updating your profile script to include /opt/jdk-12/profile.sh (for Bourne shells) or /opt/jdk-12/profile.csh (for C shells). See this FAQ for more details on how to change Java versions:

/clientarea/FAQ.ao?category=jvms&page=profile

As this is a non-LTS version, Java 12 will be supported until Java 13 is available. At that time, all uses of Java 12 will be automatically updated to Java 13.

We now support Managed MoinMoin Wiki Hosting.

We will install MoinMoin Wiki, then keep MoinMoin Wiki up-to-date on your behalf.

You have full administrative control over your MoinMoin Wiki installation.

We read the changelogs and published version compatibility, but will tend to install all available updates. We will perform a basic test of your site before and after updates, but we cannot accept responsibility for any site breaking due to these updates. We will resolve site problems on billable time, should the client not want to do this themselves.

We support four rounds of updates, nominally with round 1 on Tuesday through round 4 on Friday, but the precise schedule depends on both our workload and the schedule and urgency of the updates. The expected use-case of the four-round cycle is you may choose to have a dev site updated in round 1, then the production site updated in round 3 or 4, giving you a few days to test updates for compatibility during the weekly roll-out cycle.

We backup your MoinMoin Wiki installation (both files and database dump) before and after applying updates. Backup files are available at /var/www/site_name/var/backups/. These backup files are then replicated to additional servers both on-site and off-site per the server's configured file backup policy.

We now support Managed WordPress Hosting.

We will install WordPress, then keep WordPress, and all installed themes and plugins, up-to-date on your behalf.

You have full administrative control over your WordPress installation and may install any desired plugins and themes, including commercial premium themes. For premium themes, we may need to communicate with you regarding where to find changelogs and how to download updates.

We read the changelogs and published version compatibility, but will tend to install all available updates. We will perform a basic test of your site before and after updates, but we cannot accept responsibility for any site breaking due to these updates. We will resolve site problems on billable time, should the client not want to do this themselves.

We support four rounds of updates, nominally with round 1 on Tuesday through round 4 on Friday, but the precise schedule depends on both our workload and the schedule and urgency of the updates. The expected use-case of the four-round cycle is you may choose to have a dev site updated in round 1, then the production site updated in round 3 or 4, giving you a few days to test updates for compatibility during the weekly roll-out cycle.

We backup your WordPress installation (both files and database dump) before and after applying updates. Backup files are available at /var/www/site_name/var/backups/. These backup files are then replicated to additional servers both on-site and off-site per the server's configured file backup policy.

Python 3.4 is now end-of-life.

The following versions of Python are currently supported:

1. Python 2.7
2. Python 3.5
3. Python 3.6
4. Python 3.7

For all managed servers, we are upgrading any remaining uses of Python 3.4 to Python 3.5.

As usual, we will perform these updates during your scheduled maintenance times.

PostgreSQL 9.4 will be end-of-life on 2020-02-13 per PostgreSQL: Versioning Policy.

The following versions of PostgreSQL will be supported at the time PostgreSQL 9.4 becomes end-of-life:

1. PostgreSQL 9.5
2. PostgreSQL 9.6
3. PostgreSQL 10
4. PostgreSQL 11
5. PostgreSQL 12

We will communicate with you individually to coordinate any required upgrades before PostgreSQL 9.4 reaches end-of-life.

Once end-of-life is reached, we will upgrade any remaining uses of PostgreSQL 9.4 to PostgreSQL 9.5.

As usual, we will perform these updates during your scheduled maintenance times.

PHP 7.0 is now end-of-life.

The following versions of PHP are currently supported:

1. PHP 5.4 (CentOS 7)
2. PHP 7.1
3. PHP 7.2
4. PHP 7.3

Please review the following migration guides for this upgrade:

1. Migrating from PHP 7.0.x to PHP 7.1.x
2. Migrating from PHP 7.1.x to PHP 7.2.x
3. Migrating from PHP 7.2.x to PHP 7.3.x

For all managed servers, we are upgrading any remaining uses of PHP 7.0 to PHP 7.1.

We will carefully review all php.ini files to maintain any customizations through the upgrade. As usual, we will perform these updates during your scheduled maintenance times.