PST (3.x) has changed configuration from the previous PST (2.x). Therefore, a configuration migration is required. You cannot update PST by using \"yum update\".<\/p>\n\n\n\n
Before migrating to PST (3.x), update PST (2.x) to the latest version. Root privileges are necessary to update.<\/p>\n\n\n\n
$ sudo yum update kusanagi-prem<\/code><\/pre>\n\n\n\nor<\/p>\n\n\n\n
$ su -\n[root@kusanagi8 ~]# yum update kusanagi-prem<\/code><\/pre>\n\n\n\n<\/span>Updating PST (2.x) Profiles<\/span><\/h2>\n\n\n\nBefore migrating to PST (3.x), update all PST (2.x) enabled profiles to the latest version. You can find PST enabled profiles in PST Manager. Or, you can find them with the following root privilege commands.<\/p>\n\n\n\n
[root@kusanagi8 ~]# for i in \/home\/kusanagi\/*; do test -f $i\/wexal\/pst.config.yaml && echo $i; done\n\/home\/kusanagi\/%PROFILE-NAME%<\/code><\/pre>\n\n\n\nUpdate profiles with the PST (2.x) \"pst\" command. Note, root privileges are required to execute the PST (2.x) \"pst\" command.<\/p>\n\n\n\n
[root@kusanagi8 ~]# cd \/home\/kusanagi\/%PROFILE-NAME%\n[root@kusanagi8 %PROFILE-NAME%]# pst -v\n\nWhen the Profile Version is the same as the the Global Version:\n\nNo update is required.\n\nWhen the Profile Version is earlier than v2.4.4:\n\n[root@kusanagi8 %PROFILE-NAME%]# test -f \/etc\/httpd\/conf.d\/ssl.conf && mv \/etc\/httpd\/conf.d\/ssl.conf \/etc\/httpd\/conf.d\/ssl.conf.bak\n[root@kusanagi8 %PROFILE-NAME%]# pst init --rebuildconf\n\nIf the Profile Version is v2.4.4 or later:\n\n[root@kusanagi8 %PROFILE-NAME%]# pst init<\/code><\/pre>\n\n\n\nIf you use a reverse proxy, \"--reverseproxy\" and \"--origin options\" must also be specified in the \"pst init\" command.<\/p>\n\n\n\n
<\/span>Uninstalling the PST (2.x) Module<\/span><\/h2>\n\n\n\nFirst, uninstall the PST (2.x) module. You must have root privileges to uninstall.<\/p>\n\n\n\n
[root@kusanagi8 ~]# yum erase kusanagi-prem kusanagi-nodejs-prem kusanagi-lua-prem<\/code><\/pre>\n\n\n\n<\/span>Installing the PST (3.x) Module<\/span><\/h2>\n\n\n\nInstall the PST (3.x) module. You must have root privileges to install.<\/p>\n\n\n\n
[root@kusanagi8 ~]# yum install kusanagi-prem3<\/code><\/pre>\n\n\n\n<\/span>Configuring Initial Profile Settings<\/span><\/h2>\n\n\n\nSetup the initial profile settings to all enabled PST (2.x) profiles. The initial settings are executed with the \"pst init\" command. The profile is specified at the end of the \"pst\" command. Or, the command can be executed from the profile directory (as the current directory.) To execute the \"pst\" command,\"kusanagi\" user or root privileges are required.<\/p>\n\n\n\n
[kusanagi@kusanagi8 ~]$ pst init %PROFILE-NAME%<\/code><\/pre>\n\n\n\nor<\/p>\n\n\n\n
[kusanagi@kusanagi8 ~]$ cd \/home\/kusanagi\/%PROFILE-NAME%\n[kusanagi@kusanagi8 %PROFILE-NAME%]$ pst init<\/code><\/pre>\n\n\n\nOnce the initial PST settings are complete, the PST Manager URL will be displayed.<\/p>\n\n\n\n
pst watch stopped.\npst watch started.\nInfo: open WEXAL manager form http:\/\/xxx.xxx.xxx.xxx:61000<\/code><\/pre>\n\n\n\nThe following steps can also be performed through PST Manager. If you use PST Manager, refer to \"When Migrating from a Previous PST (2.x) - Setup in PST Manager\"<\/a> for more information.<\/p>\n\n\n\n<\/span>Enabling PST<\/span><\/h2>\n\n\n\nEnable PST for a profile that has completed the initial setup. PST is enabled with the \"pst on\" command. The profile is specified at the end of the \"pst\" command. Or, the command can be executed from the profile directory (as the current directory.) To execute the \"pst\" command,\"kusanagi\" user or root privileges are required.<\/p>\n\n\n\n
[kusanagi@kusanagi8 ~]$ pst on %PROFILE-NAME%<\/code><\/pre>\n\n\n\nor<\/p>\n\n\n\n
[kusanagi@kusanagi8 ~]$ cd \/home\/kusanagi\/%PROFILE-NAME%\n[kusanagi@kusanagi8 %PROFILE-NAME%]$ pst on<\/code><\/pre>\n\n\n\nNote that if PST has been enabled in PST (2.x), the settings will be the same.<\/p>\n\n\n\n
<\/span>Checking PST Status<\/span><\/h2>\n\n\n\nFirst, check if PST is enabled. Run the \"pst status\" command to display PST status. The profile is specified at the end of the \"pst\" command. Or, the command can be executed from the profile directory (as the current directory.) To execute the \"pst\" command,\"kusanagi\" user or root privileges are required.<\/p>\n\n\n\n
[kusanagi@kusanagi8 ~]$ pst status %PROFILE-NAME%\nWEXAL Page Speed Technology = on\nWatch = on<\/code><\/pre>\n\n\n\nor<\/p>\n\n\n\n
[kusanagi@kusanagi8 ~]$ cd \/home\/kusanagi\/%PROFILE-NAME%\n[kusanagi@kusanagi8 %PROFILE-NAME%]$ pst status\nWEXAL Page Speed Technology = on\nWatch = on<\/code><\/pre>\n\n\n\n<\/span>Modifying PST Configurations<\/span><\/h2>\n\n\n\nYou can change PST settings by editing the configuration file. The format is YAML. The configuration file is \"wexal\/pst.config.yaml\" in the profile directory. Refer to the \"PST Configuration File\"<\/a> for more information.<\/p>\n\n\n\n<\/span>Optimizing Resources<\/span><\/h2>\n\n\n\nPST Resource Monitoring Service (\"watch\") monitors changes to resources in profiles and generates optimized resource files for images, scripts, and style sheets in response to updates. However, for resources that existed in a profile before executing the initial PST configuration, an optimized resource file will not be generated until the resource is updated. Therefore, it is necessary to generate an optimized resource file for the resources in the profile.<\/p>\n\n\n\n
Run the \"pst opt all\" command to perform resource optimization. The profile is specified at the end of the \"pst\" command. Or, the command can be executed from the profile directory (as the current directory.) To execute the \"pst\" command,\"kusanagi\" user or root privileges are required.<\/p>\n\n\n\n
Resource optimization will take time if the number of resource files is large. By limiting the number of target directories to be optimized, optimization time can be shortened. The optimization time can also be shortened by using the \"pst opt image\", \"pst opt js\", and \"pst opt css\" commands instead of the \"pst opt all\" command to limit the resources to be optimized. Refer to \"PST Commands\"<\/a> for more information.<\/p>\n\n\n\nNote that optimized resource files from PST (2.x) can be used. If already optimized resource files exist, optimization will not be executed.<\/p>\n\n\n\n
[kusanagi@kusanagi8 ~]$ pst opt all %PROFILE-NAME%<\/code><\/pre>\n\n\n\nor<\/p>\n\n\n\n
[kusanagi@kusanagi8 ~]$ cd \/home\/kusanagi\/%PROFILE-NAME%\n[kusanagi@kusanagi8 %PROFILE-NAME%]$ pst opt all<\/code><\/pre>\n\n\n\nYou can check the progress of resource optimization with the \"pst queue\" command. To execute the \"pst\" command,\"kusanagi\" user or root privileges are required.<\/p>\n\n\n\n
[kusanagi@kusanagi8 ~]$ pst queue<\/code><\/pre>\n\n\n\nIf the value of the Resource Optimization Service \"optimizer\" queue is 0, resource optimization is complete. Also, you can check if there are optimized resource files under the \"wexal\/optdir\" directory in the profile. Below is an example of checking optimized resources for images uploaded in August 2021.<\/p>\n\n\n\n
[kusanagi@kusanagi8 ~]$ ls -l \/home\/kusanagi\/%PROFILE-NAME%\/wexal\/optdir\/wp-content\/uploads\/2021\/08\n-rw-r--r--. 1 root root 106707 August 3 09:50 img1-1024x640.jpg\n-rw-r--r--. 1 root root 44520 August 3 09:50 img1-1024x640.jpg.webp\n-rw-r--r--. 1 root root 137492 August 3 09:50 img1-1200x750.jpg\n-rw-r--r--. 1 root root 57288 August 3 09:50 img1-1200x750.jpg.webp\n-rw-r--r--. 1 root root 7489 August 3 09:50 img1-150x150.jpg\n-rw-r--r--. 1 root root 3782 August 3 09:50 img1-150x150.jpg.webp\n-rw-r--r--. 1 root root 204712 August 3 09:50 img1-1536x960.jpg\n-rw-r--r--. 1 root root 82396 August 3 09:50 img1-1536x960.jpg.webp\n-rw-r--r--. 1 root root 14863 August 3 09:50 img1-300x188.jpg\n-rw-r--r--. 1 root root 6956 August 3 09:50 img1-300x188.jpg.webp\n-rw-r--r--. 1 root root 66012 August 3 09:50 img1-768x480.jpg\n-rw-r--r--. 1 root root 27914 August 3 09:50 img1-768x480.jpg.webp\n-rw-r--r--. 1 root root 252283 August 3 09:50 img1.jpg\n-rw-r--r--. 1 root root 103324 August 3 09:50 img1.jpg.webp<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"PST (3.x) has changed configuration from the previous PST (2.x). Therefore, a configuration migration is required. You cannot update PST by using \"yum update\". Updating from the PST (2.x) Module Before migrating to PST (3.x), update PST (2.x) to the latest version. Root privileges are necessary to update. or Updating PST (2.x) Profiles Before migrating to PST (3.x), update all PST (2.x) enabled profiles to the latest version. You can find PST enabled profiles in PST Manager. Or, you can find them with the following root privilege commands. Update profiles with the PST (2.x) \"pst\" command. Note, root privileges are required to execute the PST (2.x) \"pst\" command. If you ... <\/p>\n