GNU Health/Upgrade

From Wikibooks, open books for an open world
Jump to navigation Jump to search

About GNU Health Upgrades

[edit | edit source]

GNU Health is in constant development. Upgrades fix bugs and keep your system with the latest functionality. Therefore, you are advised to keep your production system with the latest version.

GNU Health will always provide the scripts and tools for you to keep your health center updated.

Gathering Information

[edit | edit source]

Get the latest GNU Health versions and announces: A key point to keep your GNU Health environment in good shape is to become part of the community. We publish GNU Health version updates and other relevant news in different media. Make sure you subscribe at least to the General users and to the health announce mailing lists.

Verify your current GNU Health version: You can check your current GNU Health database version from the client, via Administration → Modules.

Checking your running GNU Health version
Checking your running GNU Health version

Always upgrade all the GNU Health modules: When we release a version, we always pack all the official modules on it. This is important, because we test the integrity and cross-functionality among modules. So, you should never use modules from different versions. For example, you should not use health_genetics version 1.6.3 with health 1.6.2 . This is not supported and can create serious inconsistencies on your database!

Prepare your Upgrade

[edit | edit source]

Plan your upgrade process, resources and downtime: Upgrading a hospital information system requires careful planning. Make sure you choose the right time, and notice your colleagues about the new release.

Test the upgrade process in another computer: It is highly recommended that you count with a separate server, where you can test your upgrade process in a controlled environment, without impacting your production installation. Write down all the steps and issues that you run into.

The Upgrade Process

[edit | edit source]

This section summarizes the upgrade process steps for a standard installation, using the modules included in the official release at FTP site. Any version specific information will sent via the mailing list, along the new release announcement, so make sure you are subscribed!

Step 1: Stop your Tryton server.

Step 2: Backup your database and GNU Health directories

 ./gnuhealth-control backup --backdir <directory> --database <dbname>

Step 3: Rename the current kernel directory, with gnuhealth user:

cd $HOME
mv gnuhealth gnuhealth_your_current_version_number

Step 4: Download the new GNU Health version. The official GNU Health tar file contains all the modules.

Step 5: Extract the kernel and follow the instructions as in a new Installation.

Step 6: Update the Tryton configuration file trytond.conf to fit your needs. Make sure you have the right values for your installation. Compare the values with your current version, they should match. Some critical variables are:

  • path

The best way to edit the configuration file is to use the GNU Health user alias editconf:


Step 7: Upgrade the database:

./trytond-admin --all --database=your_database_name

Step 8: Apply possible post-upgrade scripts at PostgreSQL level (one-time process)

You apply this step if you are upgrading from 3.0 to 3.2. Please remember to apply this script only once !

cd gnuhealth-3.2.0/scripts/upgrade/3.2
psql your_db_name < upgrade_32.sql

Step 9: Start the Tryton server:

nohup ./trytond &

You should be now in your new GNU Health version!

Patches and Patchsets · Contributing