This guide explains how to update from/to the beta branch of the UCRM project. The beta branch is intended to provide the user with the most recent UCRM features and improvements. Be advised that reverting back to the stable version is not possible. The user will only be able to update to a newer stable or beta version as it is released.
Table of Contents
- Steps - How to Migrate from Stable to Beta
- Steps - How to Revert from Beta back to Stable using Database Backup
- Steps - How to Migrate from Beta to a New Stable Version
- Related Articles
Steps - How to Migrate from Stable to Beta
Use this guide if you want to try out the beta version of UCRM.
WARNING:
- You will be able to switch back to a stable version only after a newer version of UCRM is released. E.g. moving from 2.2.2-beta1 to stable will only be possible after version 2.2.2 or higher is released. However, you can update to a newer beta version by just running the usual update command (without specifying the version).
- Moving back to a stable version if there is no newer version available, is only possible if you have the database backup of the current UCRM version.
Please, create a database backup of the current UCRM version before following these steps:
1. Make sure you have backup of your database, since there is no easy way to revert back to stable. You can get the backup in System → Tools → Database backup.
2. Access the terminal of the server where your UCRM installation is located, and run the following commands.
3. If you are switching branches (e.g. from stable to beta), you must specify the exact version number (eg. "2.2.2-beta1") in the command.
a. Ubuntu (run this as user with enabled sudo):
cd /home/ucrm
curl -fsSL https://raw.githubusercontent.com/U-CRM/billing/master/update.sh | sudo bash -s -- 2.2.2-beta1 | sudo tee update.log
b. Debian (run this as root):
cd /home/ucrm
curl -fsSL https://raw.githubusercontent.com/U-CRM/billing/master/update.sh | bash -s -- 2.2.2-beta1 | tee update.log
Steps - How to Revert from Beta back to Stable using Database Backup
UCRM does not allow users to revert to an older version. You can, however, restore the database backup of an older version. You will have to reinstall the current UCRM installation though. After that, you will be able to use the database backup of any stable version you want to restore. Follow these steps to do so:
1. Make sure you have saved a database backup of the latest stable version in a safe place.
2. Access the terminal of the server where your UCRM installation is located.
3. Stop and remove the docker containers by running the following command as root:
cd /home/ucrm
docker-compose stop
docker-compose rm --all
4. Delete your database data (make sure you have the database backup first):
rm -rf /home/ucrm/data/postgres
Note that your postgres data may be in different location if your UCRM installation comes from an old unofficial release. In this case, use this command:
rm -rf /home/ucrm/postgres
5. Run the following command to force "update" to the previous version (in this case to 2.2.1, note the "-f" parameter):
curl -fsSL https://raw.githubusercontent.com/U-CRM/billing/master/update.sh | sudo bash -s -- -f 2.2.1 | sudo tee update.log
6. Go through UCRM's setup wizard.
7. Go to System → Tools → Database backup and upload your database backup file.
8. Click the restore button for the backup you just uploaded and wait a couple of minutes.
Steps - How to Migrate from Beta to a New Stable Version
You can easily switch from beta to stable only after a newer version of UCRM is released. E.g. moving from 2.2.2-beta1 to stable will only be possible after version 2.2.2 or higher is released.
Replace the version number with the requested one and execute these commands as root:
cd /home/ucrm
curl -fsSL https://raw.githubusercontent.com/U-CRM/billing/master/update.sh | sudo bash -s -- 2.2.2 | sudo tee update.log
Related Articles