AO Logo
 
 英語 日本語
  
  
  
Developer Tools
Life Cycle
会社情報
ソフトウェア
サービス
データセンター
記事
クライアントのひろば
お問い合わせ
AO
AO Industries, Inc.
Application Infrastructure ProviderApplication Infrastructure Provider
Sign Up What's New Client Area Contact Us Site Map
 
your location:   ホームページ···新着情報
新着情報
バックナンバー一覧

日付 記述
2018/12/30

Issue #378 has been resolved, culminating in the 3.1.* releases of the memcached extension, which have allowed us to activate it in our PHP 7.3 build.

We have updated the memcached extension from version 3.0.4 to version 3.1.3 for our PHP 7.0, PHP 7.1, PHP 7.2, and PHP 7.3 builds.

2018/12/09

We now support PHP 7.3. We have compiled PHP against PostgreSQL 11.

At this time, the memcached extension is not compiling. We will enable this extension in our builds once it is updated for PHP 7.3. Please see Issue #378 for more details.

2018/12/08

We have enabled the citext module in all our active PostgreSQL builds:

2018/12/07

We now support Apache Maven 3.6. We package it as apache-maven_3, installed in /opt/apache-maven-3.

We also check for updates weekly, and deploy updates during our weekly update roll-outs.

2018/12/07

We have improved our packaging of Apache Ant:

  1. Added Provides "ant" to SPEC file.
  2. Now including library dependencies per installation recommendations.
  3. Added environment variable ANT_HOME to profile scripts.
2018/12/05

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

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

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.

2018/11/07

We now support PostgreSQL 11. 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.
2018/10/29

Tomcat 8.0 is now end-of-life.

A supported version of Tomcat, which are currently versions 7.0, 8.5, and 9.0, must be used for any existing application.

We now support in-place Tomcat upgrades to Tomcat 8.5 and above. This capability is available in AOSH through the following commands:

After performing the upgrade, please refer to the README.txt file in either /var/opt/apache-tomcat/…/README.txt (for a Multi-Site Tomcat JVM) or /var/www/…/README.txt (for a Standard Tomcat JVM). The README.txt file includes details about the auto-backup files named *.bak along with a generated command you may use to clean-up the backup files.

For all managed servers, we are upgrading to Tomcat 8.5 unless you request otherwise. We will carefully review all *.bak files to maintain any customizations through the upgrade. Applications will be restarted, possibly more than once, during this process. We will communicate with you individually and perform these updates during your usual scheduled maintenance times.

2018/10/29

Java 10 is now end-of-life.

A supported version of Java must be used for any existing application by updating your profile script. See this FAQ for more details on how to change Java versions:

https://aoindustries.com/clientarea/FAQ.ao?category=jvms&page=profile

Any uses of /opt/jdk-10/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 10 to Java 11 on their next restart.

For all managed servers, we are replacing /opt/jdk-10/profile.* with /opt/jdk-current/profile.*, as Java 10 was a non-LTS version. We are also restarting all applications currently running Java 10, so their profile scripts can select a newer version of Java. We will communicate with you individually and perform these updates during your usual scheduled maintenance times.

2018/10/28

We now support Java 11.

Java 11 may be used for any existing application by updating your profile script to include /opt/jdk-11/profile.sh. See this FAQ for more details on how to change Java versions:

https://aoindustries.com/clientarea/FAQ.ao?category=jvms&page=profile

This is a LTS version and is expected to be supported until September 2023.

In this version, we have switched to the OpenJDK builds. We are no longer using the commercial build from Oracle.

2018/08/13

We now support Python 3.7.

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

2018/08/13

We now support Python 3.6.

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

2018/08/13

We now support Python 3.5.

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

2018/08/13

We now support Python 3.4.

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

Please note that Python 3.4 End-of-life is 2019-03-16. Please consider going to Python 3.5, Python 3.6, or Python 3.7 now.

2018/07/29

We now support Java 10.

Java 10 may be used for any existing application by updating your profile script to include /opt/jdk-10/profile.sh. See this FAQ for more details on how to change Java versions:

https://aoindustries.com/clientarea/FAQ.ao?category=jvms&page=profile

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

This will be our last version using the commercial build from Oracle. In the next version, Java 11 LTS, we will be switching to the OpenJDK builds.

Due to Java version numbers no longer beginning with "1.", along with the introduction of "LTS" (long-term support) and non-LTS versions, we have split our jdk1 meta-package into jdk-lts (favoring stability by using the oldest supported LTS Java release) and jdk-current (favoring features by always having the most current Java release).

Any uses of /opt/jdk1/profile.* must be updated to either /opt/jdk-lts/profile.* or /opt/jdk-current/profile.*, depending on your choice of stability versus features.

For all managed servers, we are replacing /opt/jdk1/profile.* with /opt/jdk-lts/profile.*, as the LTS versions best match our previous release cycle. Likewise, new instances of Apache Tomcat will default to jdk-lts.

2018/07/27

We now support Tomcat 9.0 in both single-site and multi-site configurations. We have included the latest PostgreSQL JDBC Driver built for Java 8. We have also included the latest MySQL JDBC Driver 8.0.*.

2018/07/27

We now support Tomcat 8.5 in both single-site and multi-site configurations. We have included the latest PostgreSQL JDBC Driver built for Java 8. We have also included the latest MySQL JDBC Driver 8.0.*.

2018/07/17

We now support PHP 7.2. We have compiled PHP against PostgreSQL 10.

2018/07/17

We now support PHP 7.1. We have compiled PHP against PostgreSQL 9.6.

We have removed mcrypt from the build because it is deprecated in PHP 7.1. If this extension is required by your application, please Contact Us.

2018/07/17

We now support PHP 7.0. We have compiled PHP against PostgreSQL 9.4.

We now build with mysqlnd instead of depending on MySQL native libraries.

We have removed the dbase extension from this build. If this extension is required by your application, please Contact Us.

In this build, we have made the following changes to extension versions:

  1. memcached extension is now 3.*
  2. propro extension is now 2.*
  3. raphf extension is now 2.*
  4. HTTP extension is now 3.*

Older applications may need to be updated for these extension version changes before switching to PHP 7.0.

For both efficiency and security, we have switched to a more modular build of PHP, where some of the built-in extensions are built as shared libraries, packaged as separate RPMs, and only installed and enabled as-needed on a per-Apache/per-site basis. This means some extensions that were on by default in PHP 5 are now off by default in PHP 7.

We moved the default php.ini file from /opt/php-X.Y/lib/php.ini to /etc/opt/php-X.Y/php.ini, where X and Y are the major and minor versions, respectively.

We have also enabled Scan Directories with a default of /etc/opt/php-7.0/conf.d. For mod_php, this is overridden to /etc/httpd/conf/php[@instance]/conf.d for per-Apache configuration. For CGI, this is overridden to /var/www/site_name/webapps/ROOT/cgi-bin/php.d for per-site configuration.

2018/07/16

We now support MySQL 8.0.

2018/07/15

We now support PostgreSQL 10. 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.
2018/07/15

We now support PostgreSQL 9.6. 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.
  3. tsearch2 - Backwards compatibility for applications developed for versions of PostgreSQL prior to 8.3.
2018/07/14

We now support PostgreSQL 9.5. 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.
  3. tsearch2 - Backwards compatibility for applications developed for versions of PostgreSQL prior to 8.3.
2016/07/21

Created a new servlet filter to automatically strip invalid XML characters from all inputs. GET requests are 301 redirected to a URL with the characters stripped. POST, and all other methods, are simply filtered and passed along to the rest of the application.

We have added this new filter to all JSP-based web applications we are currently maintaining.

Please see com.aoindustries.servlet.filter.StripInvalidXmlCharactersFilter for more information.

2016/07/20

Separated our set of reusable servlet filters into their own project. Please see the new ao-servlet-filter project at Downloads.

2016/03/05

The default Tomcat maxPostSize setting of 2 MiB is too small for real-world data, such as pictures from modern digital cameras. We have specified a maxPostSize of 16 MiB for all Tomcat 6, 7, and 8 installations.

Please see Apache Tomcat 8 Configuration Reference, Common Attributes for more information.

2016/01/08

We now support PHP 5.6 in both 32-bit and 64-bit builds. We have compiled PHP against PostgreSQL 9.4 and MySQL 5.7.

In this build we have switched to the 2.* version of the HTTP extension. Older applications may need to be updated for this change before switching to PHP 5.6.

2016/01/07

We now support MySQL 5.7 in both 32-bit and 64-bit builds.

2016/01/06

We now support Tomcat 8.0 in both single-site and multi-site configurations. We have included the latest PostgreSQL JDBC Driver built for Java 8. We have also included the latest MySQL JDBC Driver.

2016/01/05

We now support PostgreSQL 9.4 in both 32-bit and 64-bit builds. 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.
  3. tsearch2 - Backwards compatibility for applications developed for versions of PostgreSQL prior to 8.3.
2015/02/18

We are now using Stripe for our credit card processing. Sage Payments has served us well over the years and may remain a good option for some merchants, but we are attracted to the more predictable fee structure of Stripe.

2015/02/12

Our family of sites are now all running 100% over HTTPS. Previous releases of our system supported a mixture of HTTP and HTTPS. Now all communication is encrypted for maximum security.


バックナンバー一覧
このサイトに掲載の記事・写真の無断転載を禁じます。著作権はAOインダストリーに属します。