If you are looking for install instructions, you can find them in the installation guide.

Standard Instructions

  • Backup your Agilo environment. Be sure this backup includes the Trac environment as well as the database if you don't use SQLite - you need to use external tools in that case.
  • See if you could update your Trac as well - we recommend the latest stable version (currently 0.11.7). Especially 0.11.1 - while still supported - is very slow, but is unfortunately still shipped per default on some Linux distributions. To get the latest version, just use easy_install --upgrade Trac
  • Install the new version of the Agilo egg. We recommend to use easy_install to do this as it automatically sets up all the dependencies, and unpacks all the zip-unsafe eggs correctly (beside installing the scripts into system executable paths). If you want to install into a non system directory we recommend setting the PYTHONPATH environment variable pointing to it and then using easy_install <egg_file> --install-dir=$PYTHONPATH
  • Remove the old Agilo egg.
  • Make sure that the [components] section in your Trac configuration enables Agilo Pro with these lines. (If you don't want to try the pro-version you can leave agilo_common and agilo_pro out):
     agilo.* = enabled
     agilo_common.* = enabled
     agilo_pro.* = enabled
    Please Note: Many people enable Agilo via the admin GUI for the first time, this leads to one line in the config file for each module that Agilo contains. This is bad, as it means that you have to update the config file whenever we add a new package to Agilo - or suffer from a hard to diagnose bug. Therefore, always use agilo.* = enabled to enable Agilo.
  • Restart Trac
  • If Trac tells you that its database is out of date, you need to upgrade it from the command-line with trac-admin /path/to/your/environment upgrade
  • Refresh all browser caches to make sure your browser isn't caching old css and javascript files.
  • If you experience problems on the backlog page, please read finding errors for a step-by-step-by-step instructions.

Updating from Agilo 0.8 -> 0.9 / Agilo Pro 1.{0,1,2} -> 1.3

This update requires a database upgrade so create a backup of your Agilo environment+database before installing the new version.

Afterwards perform the upgrade:

  trac-admin <env> upgrade

You don't need to do additional manual changes.

  • If you used 'Confirm Commitment' in your most recent sprint, please upgrade when this sprint ended. Otherwise the burndown chart might look wrong for the first days of this sprint.

Updating from Agilo 0.7 -> Agilo Open 0.8 / Agilo Pro 1.0

For 0.7 we had to disable some of the internal Trac modules so we could replace them with our own. We have since found a workaround that doesn't require them to be disabled anymore, so you can now re-enable them again by removing these lines from the [components] section in Trac configuration

trac.ticket.report.reportmodule = disabled
trac.ticket.query.querymodule = disabled

Upgrading from standard Trac

Agilo is fully compatible with standard Trac tickets, so you should be able to just install the Agilo egg and activate it as described above. However we recommend to always make a copy of your environment and database first so you can try it out first.

When updating from standard Trac we do replace some of Trac's internal modules, so these need to be disabled. We do have code to do this automatically, so you shouldn't need to bother. If this fails for some reason, this is what the plugins section should look like:

Core modules that need to be disabled

Please make sure that you still retain the disabled state of these core Trac plugins, or Agilo will not work correctly:

trac.ticket.api.ticketsystem = disabled
trac.ticket.roadmap.roadmapmodule = disabled
trac.ticket.web_ui.ticketmodule = disabled

The email verification module (from AccountManager) should also be disabled as it has caused numerous problems for our users. The symptom is that you see something like Warning: <acct_mgr.web_ui.MessageWrapper object at 0x024F6E30> on every page and you can not do anything even though you're logged in:

acct_mgr.web_ui.emailverificationmodule = disabled

Custom Instructions

Is there anything you had to do that we missed?

If so, please write in the Agilo Google-Group so we can include it here.

Last modified 9 years ago Last modified on 08/12/2011 09:28:15 AM

1.3.15 © 2008-2016 Agilo Software all rights reserved (this page was served in: 0.182409 sec.)