Page History

...

With my latest changes, the MXNet website will support seamless switching between API versions 0.11.0, 0.12.1, 1.0.0, 1.1.0, 1.2.1, 1.3.1, 1.4.1, 1.5.0, 1.6, and master. Currently, no higher-order releases are ready for publication, but when they are this document will outline how to add the website builds for these future releases to the master website.

There are two options when it comes to adding releases to the master website, both of which are outlined in this document. The faster route is to create a static artifact, but if future changes to the release are expected it may make more sense to create a dynamic pipeline configuration for the release in question.

In addition, it is also required to update the Apache redirect rules that set the default website version. Please see following "Update Website Default Version" section for more details.

Also note: when hosting previews on an EC2 instance, follow the instructions here to configure the server. To make all routes work properly in the latest versions of the website (>= 1.6), it is also important to modify the file /etc/httpd/conf/httpd.conf and change all instances of AllowOverride none to AllowOverride All.

...