Upgrading Source

Upgrading from Source

1. Upgrade the application

Download the new version and replace the current one with the new files. You will need to copy the bind/ integration files from the tarball to the Bind nameservers.

Make sure to retain the include/config-settings.php file (for www) and include/config-bind.php (for bind) since this contains all the application settings that are needed to connect to the databases and API.

2. Upgrade the database

MySQL database upgrades are necessary from time-to-time. You know when they are required, since NamedManager will refuse login attempts if the database is of the wrong version.

To upgrade the database, an easy to use script has been provided, which reads the settings in your configuration file, checks the current schema version of the database and then applies all the database configuration changes that are required.

$ resources/schema_update.pl -s sql/ -c htdocs/include/config-settings.php -v

The key options are:

­-s       Location of the sql/ directory.
­-c       Location of the configuration file.
-­v       Verbose – details the actions taken.

Once the SQL upgrade has been completed, you will be able to login to the application. If the upgrade is unsuccessful, users will be unable to login to prevent unexpected behaviour.

Remember that both the NamedManager web interface AND the bind integration component must be upgraded. There is not usually breakage in the API between versions, however it is risky to use different versions as it is a non-tested scenario.

After upgrading, it is recommended to check the status panel in the application to verify that zone and record data is correctly syncing to all the systems.