© 2015 X2Engine Inc.
Difference between revisions of "Software Updates and Upgrades"
(→Using the Web Updater) |
(→Using the Command Line Updater) |
||
| Line 15: | Line 15: | ||
= Using the Command Line Updater = | = Using the Command Line Updater = | ||
| + | This update method uses all of the same thoroughly-tested underpinnings and processes as the web updater, but invokes them all within a system command to the Yii console. | ||
| + | |||
| + | '''Advantages:''' safer to use, especially for large, mission-critical systems. The success of a software update or upgrade does not hinge upon a web request completing successfully. | ||
| + | |||
| + | '''Disadvantages:''' more difficult to use; requires shell access to the web server | ||
= Offline Updates = | = Offline Updates = | ||
= Manual Update and Recovery = | = Manual Update and Recovery = | ||
Revision as of 22:21, 4 December 2013
This article (currently in progress) covers the following two operations:
- updating
- Bringing an installation of X2CRM to the most recent available version
- upgrading
- Converting an existing X2CRM installation to Professional Edition
Contents
Using the Web Updater
The web updater can be accessed using the link in the notification message at the top of the window in versions later than 3.5.5, or by going to the Admin page and clicking the "Update" button at the top, in earlier versions.
Advantages: it is generally quicker and easier to use, and it does not require shell/SSH access to the web server.
Disadvantages: it is not recommended for use on large installations of X2CRM, i.e. containing over a million records.
Explanation: The inherent weakness of the web updater (or any web-based updater to any web application) is that it must always rely upon web requests to the server, and it thus must perform extremely critical operations for the update all within the scope of a web request. Web requests, it goes without saying, are not always reliable. For example, one's internet connection might get cut off due being on a wireless network and encountering interference. Furthermore, if any operations take an exceedingly long amount of time, e.g. because of the size of the data set on which the update must operate, the web request for those operations may take longer than the configured server timeout (maximum request time). This would potentially cut short the execution of a critical update stage, and thus the update would require manual completion and recovery.
Using the Command Line Updater
This update method uses all of the same thoroughly-tested underpinnings and processes as the web updater, but invokes them all within a system command to the Yii console.
Advantages: safer to use, especially for large, mission-critical systems. The success of a software update or upgrade does not hinge upon a web request completing successfully.
Disadvantages: more difficult to use; requires shell access to the web server
