This section explains how to upgrade an existing Emilda setup to 1.2.x. Below you'll find instructions on how to upgrade between different versions. If you upgrade from an older version, you should follow each step in the progress, i.e. upgrading from 1 -> 3 you would do 1 -> 2, 2 -> 3. Make sure you read the right sections and do the right steps to achieve a fully working Emilda environment.
Emilda 1.2.x releases are stable bug fix releases. As such, they only fixes a few minor code issues. Upgrading to 1.2.x can be done by simply overwriting the contents of the existing src folder with the contents of the new src folder (make sure you don't have anything else than source files in that folder).
The easiest way, however, is to use the supplied 1.2.x patch. Download the patch, save it in your current emilda src folder (the one with all the .php files) and issue the following command (in the src folder):
gunzip emilda-1.2.x.patch.gz patch -p2 < emilda-1.2.x.patch
If there is an emilda-1.2.x-lang.patch.gz file available, the language files have changed too. Download this patch, save it in your emilda lang folder and issue the following command (in the lang folder):
gunzip emilda-1.2.x-lang.patch.gz patch -p2 < emilda-1.2.x-lang.patch
After this the new language files need to be compiled as usual.
Watch out for any errors or warnings. After this run setup.php to make sure your system is up-to-date. If everything was successful, you should have a working Emilda 1.2.x environment.
This is only required for Emilda 1.2.1.
The zebra folder has changed in 1.2.1. Turn off your zebra server. Make sure you don't loose your records folder and replace your existing zebra folder with the new one (the tab/bib1.att file has changed). After the upgrade issue the following commands in the zebra root folder:
zebraidx init zebraidx -g emilda update records zebraidx commit
If everything went smoothly, restart zebra.
Always make a backup of your database before upgrading!
The easiest way to upgrade the Emilda source is probably to move the old directory to a backup location, install the new source from the tarball and copy over required files from the old installation. Here's an example:
mv emilda emilda-1.1 tar -zxf emilda-1.2.tar.gz mv emilda-1.2/src emilda cp emilda-1.1/config emilda/conf/ cp emilda-1.1/MARC_config emilda/ cp emilda-1.1/MARC_defs emilda/ cp emilda-1.1/MARCsyn_config emilda/ cp -a emilda-1.1/perl/barcodes/* emilda/perl/barcodes/Also copy/move over any other files/directories you may have in the old emilda dir that didn't come with the original tarball. If you have the Zebra database in the emilda-1.1 directory, move it to the new emilda directory. The MARC* files you copied over are only needed for the Upgrade part (setup.php) and can be safely removed after the upgrade.
Now point your Internet browser to http://your-old-emilda-address/setup.php and follow the on-screen instructions. After a successful setup your Emilda database will have been converted to the right version. Now you should edit config in the Emilda directory and remove everything except the MySQL section, as the rest is in the database now. Remember to disallow access to setup.php after completing the installation!
Note: MARC configuration has been moved to the database also but setup.php won't convert any changes you might have made to the old MARC_config file. After a successful upgrade you should log in to Emilda and modify MARC settings from the configuration panel if you made any changes to the old file.
To get languages working correctly, upgrade your locale linkage folders in the ./locale folder. You do this by going into the Emilda source folder and executing the following command:
sh bin/locales.shIn addition you need to compile the languages to support these. This is done by going into the source folder and executing the following command:
sh bin/compile_languages.sh
Upgrading Zebra is almost identical to when installing a new Emilda environment. To ensure that all files that have been updated are present on your system, we encourage you to download this tarball, and operate as follows.
- Move your existing zebra folder to another location, but be sure not to delete it yet as this would result in you loosing all your records.
- Extract the tarball to the same location where you had the old one, with the same name and same permissions.
- Copy your records folder (typically records/) from your old zebra folder. If you have made any custom changes to your Emilda instance, you probably are so familiar with Zebra that you will figure out which files you need to restore from your old folder to be able to use those changes. Just make sure that also the "new" issues released will be taken into consideration. Now you can theoretically delete your old zebra folder, but it might be a good idea to hold on to it until you are certain that everything works.
- Initialize and update your new Zebra instance by issuing the following set of commands:
- Go into the Zebra root folder: "cd /path/to/emilda/zebra/
- Init Zebra: "zebraidx init"
- Index the records/ folder: "zebraidx -g emilda update records"
- Commit results into shadow: "zebraidx commit"
- Start the zebrasrv-process: "zebrasrv -l /path/to/log @:9999"
As you might notice the syntax has slightly changed, so if you have any scripts or similar that run Zebra at startup it might be a good idea to make these compatible with the new system.
Always make a backup of your database before upgrading!
The easiest way to upgrade the Emilda source is probably to move the old directory to a backup location, install the new source from the tarball and copy over required files from the old installation. Here's an example:
mv emilda emilda-1.1 tar -zxf emilda-1.2-alpha.tar.gz mv emilda-1.2-alpha/src emilda cp emilda-1.1/config emilda/ cp -a emilda-1.1/perl/barcodes/* emilda/perl/barcodes/Also copy/move over any other files/directories you may have in the old emilda dir that didn't come with the original tarball. If you have the Zebra database in the emilda-1.1 directory, move it to the new emilda directory.
Now point your Internet browser to http://your-old-emilda-address/setup.php and follow the on-screen instructions. After a successful setup your Emilda database will have been converted to the right version. Now you should edit config in the Emilda directory and remove everything except the MySQL section, as the rest is in the database now. Remember to disallow access to setup.php after completing the installation!
Note: MARC configuration has been moved to the database also but setup.php won't convert any changes you might have made to the old MARC_config file. After a successful upgrade you should log in to Emilda and modify MARC settings from the configuration panel if you made any changes to the old file.
Upgrading Zebra is almost identical to when installing a new Emilda environment. To ensure that all files that have been updated are present on your system, we encourage you to download this tarball, and operate as follows.
- Move your existing zebra folder to another location, but be sure not to delete it yet as this would result in you loosing all your records.
- Extract the tarball to the same location where you had the old one, with the same name and same permissions.
- Copy your records folder (typically records/) from your old zebra folder. If you have made any custom changes to your Emilda instance, you probably are so familiar with Zebra that you will figure out which files you need to restore from your old folder to be able to use those changes. Just make sure that also the "new" issues released will be taken into consideration. Now you can theoretically delete your old zebra folder, but it might be a good idea to hold on to it until you are certain that everything works.
- Initialize and update your new Zebra instance by issuing the following set of commands:
- Go into the Zebra root folder: "cd /path/to/emilda/zebra/
- Init Zebra: "zebraidx init"
- Index the records/ folder: "zebraidx -g emilda update records"
- Commit results into shadow: "zebraidx commit"
- Start the zebrasrv-process: "zebrasrv -l /path/to/log @:9999"
As you might notice the syntax has slightly changed, so if you have any scripts or similar that run Zebra at startup it might be a good idea to make these compatible with the new system.
Always make a backup of your database before upgrading!
The easiest way to upgrade the Emilda source is probably to move the old directory to a backup location, install the new source from the tarball and copy over required files from the old installation. Here's an example:
mv emilda emilda-1.2-alpha tar -zxf emilda-1.2-beta.tar.gz mv emilda-1.2-alpha/src emilda cp emilda-1.2-alpha/config emilda/ cp -a emilda-1.2-alpha/perl/barcodes/* emilda/perl/barcodes/Also copy/move over any other files/directories you may have in the old emilda dir that didn't come with the original tarball. If you have the Zebra database in the emilda-1.1 directory, move it to the new emilda directory.
Now point your Internet browser to http://your-old-emilda-address/setup.php and follow the on-screen instructions. After a successful setup your Emilda database will have been converted to the right version. You may want to disallow access to setup.php after completing the installation, although, nothing harmful can be done with it after a successfull installation.
Always make a backup of your database before upgrading!
The easiest way to upgrade the Emilda source is probably to move the old directory to a backup location, install the new source from the tarball and copy over required files from the old installation. Here's an example:
mv emilda emilda-1.2-beta tar -zxf emilda-1.2-rc1.tar.gz mv emilda-1.2-rc1/src emilda cp emilda-1.2-beta/config emilda/ cp -a emilda-1.2-beta/perl/barcodes/* emilda/perl/barcodes/Also copy/move over any other files/directories you may have in the old emilda dir that didn't come with the original tarball. If you have the Zebra database in the emilda-1.1 directory, move it to the new emilda directory.
Move the config file to the conf directory (mv config conf/). Now point your Internet browser to http://your-old-emilda-address/setup.php and follow the on-screen instructions. After a successful setup your Emilda database will have been converted to the right version. You may want to disallow access to setup.php after completing the installation, although, nothing harmful can be done with it after a successfull installation.
To get languages working correctly, upgrade your locale linkage folders in the ./locale folder. You do this by going into the Emilda source folder and executing the following command:
sh bin/locales.shIn addition you need to compile the languages to support these. This is done by going into the source folder and executing the following command:
sh bin/compile_languages.sh