You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

v1.0.0 makes several changes that will simplify future upgrades. Unfortunately, this means the upgrade from v0.9.4 to v1.0.0 will require some extra manual steps. If you are running v0.9.3 or older, make sure to upgrade to v0.9.4 first before upgrading to v1.0.0.

Relink /tmp Directory

As of Registry v1.0.0, app/tmp is a symlink to local/tmp. Update local/tmp to point to your tmp directory. You may need to rmdir local/tmp before creating a new symlink.

Copy Configurations

As of Registry v1.0.0, configuration files that must be modified locally are placed under local/Config, with symlinks from app/Config pointing to them. Copy the following files from your previous installation to local/Config:

  • database.php
  • email.php
  • security.salt
  • security.seed

Web Server Authentication

If you were previously using .htaccess files to protect registry/app/webroot/auth/login, it is recommended that you move the configuration into httpd.conf to simplify future upgrades.

Shibboleth Embedded Discovery Service (EDS)

As of Registry v1.0.0, the EDS is no longer a Plugin, but is supported in the core code. This requires some changes:

  1. The EDS must be re-configured.
  2. The URL for the EDS has changed, and most likely your SP will need to be re-configured with the new URL.

For more information about these changes, see Configuring the Shibboleth Embedded Discovery Service Plugin.

Custom Plugins

Any custom Plugins should be moved to local/Plugin to facilitate future upgrades.

  • No labels