Agilefant.org

1. Download the release

Migrating other databases The migration script from previous versions is written for MySQL only. If you use a different database and succeed in migrating, please provide the needed changes to our forum.

First of all, download the public release of Agilefant from the Downloads section.

Change the database.properties file accordingly to match your MySQL settings. See Installation Guide for more.

2. Migrating the database

Be careful when migrating Because of the still uncomplete functionality of the Agilefant 2.0, the migration script will lose some of your data. Make sure you take a backup of your database before migration.

Before you start, take a backup of your database. This can be done e.g. with the mysqldump tool.

$ mysqldump -u[username] -p[password] [database_name] > [dump-name].sql
E.g.
$ mysqldump -uagilefant -pagilefant agilefant > dump-agilefant-2009-10-01.sql

Locate the update scripts inside the .zip package /doc/sql/updates -folder. If you're migrating from version 1.6.x, you need to run only the script 160-200.sql.

Inside MySQL client:
> use agilefant;
> source ~/160-200.sql    # From the folder you have it in

2.1 What to do if the schema name is not 'agilefant'?

The migration script rebuilds the indexes of the database. Therefore, the script needs to know which database to look for.

Find the following row from the beginning of the 160-200.sql update script:

SET @SCHEMA_NAME = 'agilefant';

And change it to

SET @SCHEMA_NAME = '<your_schema_name>';

After changing the SCHEMA_NAME variable, your script should work fine.

3. Deploying the Agilefant

See Installation Guide