Additions:
- Deal with any necessary changes to ownership and file or directory permissions. For example, for a Linux site, if your site has well chosen umask, then the file and directory permissions will not need changing. But if you unarchive as root, you will need to change the ownership of the files. If the site is running scripts as the user named mysite with group mysite, then from the root directory of the site, you could use the command chown -R mysite:mysite * to put the files into the owership of the site user. If you unarchive as the site user, then no change will be needed.
Deletions:
- Deal with any necessary changes to ownership and file or directory permissions. For example, for a Linux site, if your site has well chosen umask, then the file and directory permissions will not need changing. But if you unarchive as root, you will need to change the ownership of the files. If the site is running scripts as the user named mysite, then from the root directory of the site, you could use the command chown -R mysite:mysite * to put the files into the owership of the site user. If you unarchive as the site user, then no change will be needed.
Additions:
- Unarchive the bare Aliro distribution in the root directory of your Aliro site. Overwrite existing files. If a zip archive is used, you will be prompted what to do about new files with the same names as existing, and you can reply A to ovewrite all. If a tar.gz archive is used on a Linux system, you can force overwriting by using the command tar --overwrite -xzvf anAliroArchive.tar.gz (adjusting the name of the archive as appropriate).
- Deal with any necessary changes to ownership and file or directory permissions. For example, for a Linux site, if your site has well chosen umask, then the file and directory permissions will not need changing. But if you unarchive as root, you will need to change the ownership of the files. If the site is running scripts as the user named mysite, then from the root directory of the site, you could use the command chown -R mysite:mysite * to put the files into the owership of the site user. If you unarchive as the site user, then no change will be needed.
Deletions:
- Unarchive the bare Aliro distribution in the root directory of your Aliro site. Overwrite existing files. If a zip archive is used, you will be prompted what to do about new files with the same names as existing, and you can reply A to ovewrite all. If a tar.gz archive is used on a Linux system, you can force overwriting by using the command tar --overwrite -xzvf anAliroArchive.tar.gz (adjusting the name of the archive as appropriate).
- Deal with any necessary changes to ownership and file or directory permissions. For example, for a Linux site, if your site has well chosen umask, then the file and directory permissions will not need changing. But if you unarchive as root, you will need to change the ownership of the files. If the site is running scripts as the user named mysite, then from the root directory of the site, you could use the command chown -R mysite:mysite * to put the files into the owership of the site user. If you unarchive as the site user, then no change will be needed.
Additions:
- Unarchive the bare Aliro distribution in the root directory of your Aliro site. Overwrite existing files. If a zip archive is used, you will be prompted what to do about new files with the same names as existing, and you can reply A to ovewrite all. If a tar.gz archive is used on a Linux system, you can force overwriting by using the command tar --overwrite -xzvf anAliroArchive.tar.gz (adjusting the name of the archive as appropriate).
Deletions:
- Unarchive the bare Aliro distribution in the root directory of your Aliro site. Overwrite existing files. If a zip archive is used, you will be prompted what to do about new files with the same names as existing, and you can reply A to ovewrite all. If a tar.gz archive is used on a Linux system, you can force overwriting by using the command tar --overwrite -xzvf AliroArchive.tar.gz (adjusting the name of the archive as appropriate).
Upgrading the Aliro Core Software
The Aliro software is steadily evolving, and there will be a need to upgrade a site from time to time. Every effort has been made to simplify this operation.
Automatic Upgrading
When a site is running Aliro beta 7 or above, the automatic upgrade mechanism can be used. This brings information from a central upgrade site to the local system, subject to administrator review. Upgrade is invoked by someone signed in as Super Administrator. The first step is to go to the Manage Site - Configuration - menu item (although this is likely to be moved to being an individual menu item in future). From here the steps are:
- Click on the "Start Upgrade" toolbar item. The operation will take some time, because the local Aliro system creates a manifest of what files are installed and then sends it to the upgrade site, to receive back an upgrade package. In future, the choice of upgrade site will be selected by the administrator, but at present it is hard coded to go to http://upgrade.aliro.org∞.
- Once the upgrade package is received, you will be shown a report which consists of a list of files split into three groups. There is a list of files to be added to the local site, a list of files to be updated on the local site, and a list of files to be deleted from the local site. The full path of each file is given. Against each file is a checkbox that is ticked. You should untick the checkbox for any file action that you do not want to happen.
- When the list of file actions has been reviewed, click on the "Complete Upgrade" toolbar item. The actions should be completed and the site should be at the same level as the upgrade site.
The vast majority of the upgrade logic is incorporate into the core of Aliro. You can create your own upgrade site by setting up an Aliro site and installing com_upgrader into it. Please note that com_upgrader has the name of the administrator directory hard coded into it, because it runs on the user side and otherwise has no knowledge of the admin side, which is needed for upgrade operations. You must modify the directory name coded into com_upgrader if your upgrade site is using an administrator directory with a name different from "administrator".
Manual Upgrading
For a major change or to bring a site up to date from a release prior to beta 7, the manual upgrade process should be followed. The Aliro code from beta 7 onwards has been carefully developed to be able to bring earlier sites up to date with the minimum of disruption, including making alterations to the database. Please follow these steps to complete a manual upgrade:
- The upgrade should be done with a bare Aliro package that does not include bundled applications. Upgrade of applications should be done separately by installing a new version of the application package, ticking the "upgrade" box in the installer interface.
- Log out from the site
- Rename the site's administrator directory back to "administrator" if it has been changed. (Or build your own Aliro distribution package with the directory name of your choice).
- Unarchive the bare Aliro distribution in the root directory of your Aliro site. Overwrite existing files. If a zip archive is used, you will be prompted what to do about new files with the same names as existing, and you can reply A to ovewrite all. If a tar.gz archive is used on a Linux system, you can force overwriting by using the command tar --overwrite -xzvf AliroArchive.tar.gz (adjusting the name of the archive as appropriate).
- Deal with any necessary changes to ownership and file or directory permissions. For example, for a Linux site, if your site has well chosen umask, then the file and directory permissions will not need changing. But if you unarchive as root, you will need to change the ownership of the files. If the site is running scripts as the user named mysite, then from the root directory of the site, you could use the command chown -R mysite:mysite * to put the files into the owership of the site user. If you unarchive as the site user, then no change will be needed.
- Change the administrator directory name if you wish
- Log in as administrator - you may see a few errors, but they should be minor
- Go to the Manage Site - Configuration - menu option, review the configuration and save. This should clear errors that were caused by the old configuration being out of date
- If possible, carry out the automatic upgrade procedure described above, as this will delete any obsolete core files
- Go to the Manage Site - Error Reports - menu option and review any errors recorded there. If none look serious, then delete all to start with a clean slate.
- That completes the upgrade.