About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
installation:migration_notes

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
installation:migration_notes [2016/05/25 14:17] – [Migrating from VuFind 2.x to the Latest Release] demiankatzinstallation:migration_notes [2018/12/19 17:03] – [VuFind Migration Notes] demiankatz
Line 2: Line 2:
  
 This page provides notes on upgrading to the latest VuFind release from earlier versions. This page provides notes on upgrading to the latest VuFind release from earlier versions.
- 
-// Notes on upgrading to the latest VuFind 1.x can be found on the [[legacy:installation:migration_notes|legacy migration notes]] page. // 
  
 ===== Migrating from VuFind 2.x or Newer to the Latest Release ===== ===== Migrating from VuFind 2.x or Newer to the Latest Release =====
Line 17: Line 15:
 Starting with VuFind 2.1, after unpacking the new VuFind, you should follow these steps to be sure your database and configurations are fully updated: Starting with VuFind 2.1, after unpacking the new VuFind, you should follow these steps to be sure your database and configurations are fully updated:
  
-  - Unpack the new version of VuFind on top of the old version. This will most commonly involve simply downloading the new version, but if you are using Git for version control, it can also be achieved by checking out a different version tag.+  - Unpack the new version of VuFind on top of the old version. This will most commonly involve simply downloading the new version, but if you are using Git for version control, it can also be achieved by checking out or merging a different version tag
 +    - :!: If you are simply downloading the new version rather than using Git, it is safer to delete non-customized files before unpacking, to ensure that obsolete files do not remain as part of your installation -- this is particularly important for the solr/vendor directory. 
 +  - If you are installing from Git rather than a downloaded archive, run "composer install" to update dependencies.
   - Make sure that the config/vufind subdirectory of your [[configuration:local_settings_directory|local settings directory]] may be written by the web server and that autoConfigure is turned on in the [System] section of [[configuration:files:config.ini]].   - Make sure that the config/vufind subdirectory of your [[configuration:local_settings_directory|local settings directory]] may be written by the web server and that autoConfigure is turned on in the [System] section of [[configuration:files:config.ini]].
   - Empty out the cache subdirectory of your [[configuration:local_settings_directory|local settings directory]] to be sure no incompatible settings are cached.   - Empty out the cache subdirectory of your [[configuration:local_settings_directory|local settings directory]] to be sure no incompatible settings are cached.
Line 32: Line 32:
 :!: If you upgrade by reinstalling the DEB package instead of simply unpacking a .zip or .tar.gz archive, be aware that some defaults (particularly in local/httpd-vufind.conf) may be restored. As with other configuration overwriting, backup files should exist that may be easily compared/restored if this causes problems. :!: If you upgrade by reinstalling the DEB package instead of simply unpacking a .zip or .tar.gz archive, be aware that some defaults (particularly in local/httpd-vufind.conf) may be restored. As with other configuration overwriting, backup files should exist that may be easily compared/restored if this causes problems.
  
-Note that Java 1.is required starting with VuFind 2.3.+:!: Make sure that your system meets the [[installation:requirements|requirements]] of the new version. 
 + 
 +=== Special Notes on Upgrading with PostgreSQL === 
 + 
 +VuFind's web-based upgrade script will automatically fix your MySQL database structure for you to account for changes. However, for PostgreSQL, database migrations must be applied manually. Look in the module/VuFind/sql/migrations/pgsql directory to see if there is a migration folder for the new release. If so, the scripts in the migration folder should be applied in numeric order from the command line. You can do this with the command: 
 + 
 +<code>psql -U [your-vufind-username] -d [your-vufind-database-name] -a -f [path/to/migration.sql]</code> 
 + 
 +=== Special Notes on Upgrading from 2.x to 3.x === 
 + 
 +VuFind 2.x uses Solr 4 while VuFind 3.x uses Solr 5. If you are upgrading from 2.x to 3.x, you will notice some important changes: the solr directory contents will be structured differently, and the VuFind start/stop script will be called "solr.sh/solr.bat" instead of "vufind.sh/vufind.bat"
 + 
 +Before unpacking the 3.x distribution on top of 2.x, it is recommended that you follow these steps: 
 + 
 +- Delete vufind.sh/vufind.bat to prevent confusion. If you wish to retain these script names for your existing workflows, create simple wrapper scripts around solr.sh/solr.bat 
 +- Rename your existing solr directory to solr_old (this way you can easily revert if you have problems with the upgrade; after successfully reindexing your data and testing your upgraded VuFind, you can remove the solr_old directory).
 ===== Migrating from VuFind 1.x ===== ===== Migrating from VuFind 1.x =====
  
installation/migration_notes.txt · Last modified: 2024/02/07 15:47 by demiankatz