Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
litespeed_wiki:admin:lsup [2019/04/09 19:07]
Lisa Clarke Copyediting
litespeed_wiki:admin:lsup [2023/04/14 19:14] (current)
Lisa Clarke Redirect to new Documentation Site
Line 1: Line 1:
-====== The "​lsup"​ Command ====== +~~REDIRECT>​https://docs.litespeedtech.com/​lsws/​updates/~~
- +
-If an update is unavailable in your control panel (or you just prefer the command line), you can update LSWS from the terminal. +
- +
-The ''​lsup''​ command is a simple way to update LiteSpeed Web Server from the command line, allowing the possibility of upgrading hordes of LSWS installations with a single command. +
- +
-===== Location ===== +
- +
-The ''​lsup''​ command is located at ''​$SERVER_ROOT/​admin/​misc/​lsup.sh''​. In most CentOS installations,​ the command is thus: +
- +
-  /​usr/​local/​lsws/​admin/​misc/​lsup.sh +
- +
-===== Function ===== +
- +
-Running the basic ''​lsup''​ command will automatically upgrade your installation of LiteSpeed Web Server to the latest release. There are also options for customizing the command listed below. +
- +
-===== Options ===== +
- +
-  * ''​-f'':​ If you already have the version to be installed, the basic ''​lsup''​ command will abort. The ''​-f''​ option forces ''​lsup''​ to install even if the version you have is the same version as the LSWS to be installed. This can be useful if there has been a change in the build since you upgraded, but a new build has not yet been released. +
-  * ''​-v'':​ You can control what version you install with the ''​-v''​ option followed by a version number. (For example: ''​./​lsup.sh -v 5.3.4''​) This will allow you to downgrade to older versions if you run into a bug. Keep in mind, LiteSpeed only keeps the most recent few versions available. Much older versions are not available. +
-  * ''​-b'':​ Designates a build number. All versions start from build ''​0''​. To view what build you are currently using, view ''/​usr/​local/​lsws/​autoupdate/​build''​. Will automatically upgrade to the latest build of the designated version if ''​-b''​ is not set. (Only available for versions 5.0 and higher.) +
- +
-**NOTE**: for ''​-v''​ and ''​-b'',​ you can look up a version/​build number [[https://www.litespeedtech.com/​products/​litespeed-web-server/​release-log|here]] if you need to. +
- +
-===== Example ===== +
- +
-Force an update to version 5.3.4: +
-<​code>/​usr/​local/lsws/admin/misc/​lsup.sh -f -v 5.3.4</​code>​ +
- +
-Force an update to version 5.3.4 build 4: +
-<​code>/​usr/​local/​lsws/​admin/​misc/​lsup.sh -f -v 5.3.4 -b 4</​code>​ +
- +
-====== Stable Tier vs. Edge Tier ====== +
-Starting from version 5.3.7 build 4, LiteSpeed Web Server introduces tiers to meet your auto upgrade requirements through the ''​lsup.sh''​ script. This will make your server more stable during the upgrade, while still keeping edge users in mind. Here's how it works: +
- +
-  * The ''/​usr/​local/​lsws/​autoupdate/​follow_stable''​ marker will be set automatically when you upgrade to 5.3.7 build 4 or a later version. +
-  * If you want to set up a cron job, please use ''​lsup.sh''​ without any parameters instead of using ''​lsup.sh -f''​. +
-  * ''​lsup.sh''​ without a parameter will follow the Stable Tier if the ''​follow_stable''​ marker is set, and the Stable Tier number is controlled. +
-  * ''​lsup.sh -f''​ will install the edge build, which is the latest build available, and it will stop following the Stable Tier by removing the ''​follow_stable''​ marker. +
-  * If a particular version is forced, such as with ''​lsup.sh -f -v <​version>'',​ the ''​lsup.sh''​ command without parameters will stop following the Stable Tier, and will do nothing.  +
-  * To start following the Stable Tier again, you can manually create a ''​follow_stable''​ marker by running ''​touch /​usr/​local/​lsws/​autoupdate/​follow_stable''​. +
-  * Why is ''​follow_stable''​ important? When you try to install a test build/debug build, or downgrade to an older version, you certainly do not want ''​lsup.sh''​ in your daily cron job to change the version to the Stable Tier automatically during the test. In these situations, unsetting ''​follow_stable''​ will make ''​lsup.sh''​ do nothing in a cron job.  +
-  * Please be aware that the new powerful Stable/Edge Tier system is only available in ''​lsup.sh''​ for version 5.3.7 build 4 and later. If you force a downgrade to an earlier version/​build,​ it will not have the above feature. +
- +
  • Admin
  • Last modified: 2019/04/09 19:07
  • by Lisa Clarke