Galaxy Maintenance

Maintaining a Galaxy instance is important to do, something that cannot be understated.

Security Notices

If you maintain a public instance of Galaxy it is recommended to sign up for the public servers mailing list to receive security fixes with priority. Also consider adding your instance to the Galaxy Platform Directory so more people can discover it.

General Update Procedures

Many admins update to each new release, though update frequency largely depends on your local instance's needs (e.g. new Galaxy features your users will want) and how much disruption your user base will tolerate (in terms of downtime + UI changes, etc)

  1. Read release notes and look for possible breakage, security fixes, new features,
  2. Update code to the chosen release branch (release_17.01 here).

    • New Galaxy repository: $ git clone -b release_17.01
    • Update of existing repository: $ git checkout release_17.01 && git pull --ff-only origin release_17.01
  3. Run ./scripts/ before restarting the server to update Galaxy's virtualenv
  4. (when prompted) Update Galaxy database

    • Backup Galaxy database (e.g. pg_dump -U <username> <database> > galaxy-backup-$(date "+%s").sql).
    • Migrate your DB with sh upgrade.
  5. Search conflicts and resolve (check git status),
  6. Diff config/galaxy.ini and config/galaxy.ini.sample to check for possible new features/changes,
  7. In general all config files should be merged with the *.sample files.

    • meld is a good graphical editor for this
    • some of us prefer something like vimdiff
  8. (when prompted) Run tool migration scripts (e.g. sh ./scripts/migrate_tools/ install_dependencies).
  9. Notify your user group and share the release notes.