Update 06-12-2024
Due to the wide impact of the planned changes in KUSANAGI 9.5.0, we have decided to postpone some of the changes that were originally announced on 05-27-2024 to be made after KUSANAGI 9.5.0.
For details on the postponed changes, please refer to Planned changes after "KUSANAGI 9.5.0".
In addition, with the release of Nginx 1.27, the default Nginx version change will be moved forward.
"KUSANAGI 9.5.0"
In addition to the existing KUSANAGI, built on the latest versions of AlmaLinux OS 8, CentOS Stream 9 and AlmaLinux OS 9, this change will allow for a wider selection of middleware.
- In addition to the middleware provided by KUSANAGI, it will also be possible to use middleware provided by the base OS or by third parties as-is.
Changes in “KUSANAGI 9.5.0”
Change in default Nginx version
Nginx 1.25, which was the default version until KUSANAGI 9.4.15, is no longer supported by the community with the release of Nginx 1.27. The default will be changed to Nginx 1.27 in KUSANAGI 9.5.0.
If --nginx127
, --nginx126
, --nginx125
, --nginx124
, and --httpd24
are not specified in the kusanagi init command, the default web server is --nginx127
(Nginx 1.27).
Service name changed for Nginx 1.26/1.27
The Nginx service name will be changed to nginx126.service
in Nginx 1.26 and nginx127.service
in Nginx 1.27 respectively.
Also, the service name of future versions of Nginx will be changed to nginxXXX.service
(where XXX
is the version).
Note that the service names up to Nginx 1.25 will remain as nginx.service
.
Because of this change, when targeting Nginx on KUSANAGI with the systemctl command, it is necessary to specify a service name that matches the version of Nginx you are using.
To restart and reload Nginx 1.26/1.27
Use kusanagi nginx command instead of systemctl command.
The kusanagi nginx command can also be used for Nginx 1.24/1.25.
To restart
# systemctl restart nginx
↓
# kusanagi nginx
To reload
# systemctl reload nginx
↓
# kusanagi nginx --reload
Path name changed for Nginx 1.26/1.27
The Nginx path name will be changed to /opt/kusanagi/nginx126/sbin/nginx
for Nginx 1.26 and /opt/kusanagi/nginx127/sbin/nginx
for Nginx 1.27 respectively.
Also, the path name of future versions of Nginx will be changed to /opt/kusanagi/nginxXXX/sbin/nginx
(where XXX
is the version).
Note that the path names up to Nginx 1.25 will remain as /opt/kusanagi/sbin/nginx
.
To test Nginx 1.26/1.27
Use kusanagi nginx command instead of nginx command.
The kusanagi nginx command can also be used for Nginx 1.24/1.25.
To test
# /opt/kusanagi/sbin/nginx -t
↓
# kusanagi nginx --test
Planned changes after "KUSANAGI 9.5.0"
The following changes will be supported after KUSANAGI 9.5.0.
- It will be possible to combine and operate multiple versions of middleware provided by KUSANAGI.
Changes in configuration file paths for Nginx
After KUSANAGI 9.5.0, we plan to make it possible to install multiple versions of Nginx at the same time, which was not possible in previous releases. In line with this, we plan to change theconfiguration file paths for Nginx to /etc/opt/kusanagi/nginxXXX
(where XXX
is the version).
Changes in service names and configuration file paths for other middleware
After KUSANAGI 9.5.0, we plan to make it possible to install multiple versions of PHP at the same time, which was not possible in previous releases. In line with this, we plan to change the service name and configuration file paths for PHP as well as Nginx.
Details regarding the change of PHP service names and configuration file paths will be announced separately.