Upgrading Git

Handling Upgrades from Git

If you installed NamedManager from Git you will get more frequent updates than users on supported releases.

Most of the changes will be code only but there will sometimes be database changes such as additional translations.

1. Upgrade the application

You can update to the latest source in Git at any stage by running git pull which will download and merge all the changes.

If you have been working on your own customisations, this update command will allow you to merge them with the new version.

The best way to avoid having to do complex merges is of course by contributing back upstream as often as possible. :-)

2. Upgrade the database

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.