ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Document migrating from Redmine to ChiliProject (Task #222)


Added by Eric Davis at 2011-02-25 12:03 am. Updated at 2011-02-26 11:32 pm.


Status:Closed Start date:2011-02-25
Priority:High Due date:
Assignee:Eric Davis % Done:

0%

Category:Documentation
Target version:1.1.0 — Bell
Remote issue URL:

Description


History

Updated by Derek Montgomery at 2011-02-26 04:32 pm

Feeling lazy right now to put it properly in wiki so I'll paste it here to not forget.

from redmine stable 1.1.1

Gentoo Linux 64bits

apache 2.2
mysql 5.1
passenger 3.0.2
ruby 1.8.7
rubygems 1.3.7
actionmailer (2.3.5)
actionpack (2.3.5)
activerecord (2.3.5)
activeresource (2.3.5)
activesupport (2.3.5)
i18n (0.4.2)
mysql (2.8.1)
rack (1.2.1, 1.0.1)
rails (2.3.5)
rake (0.8.7)
rmagick (2.13.1)
ruby-openid (2.1.8)

14:54:50     | ofc backuped up files and db
14:55:22     | copied config/{configuration,database,additional-environment}.yml files
14:55:26     | copied plugins
14:55:29     | copied themes
14:55:34     | copied files
14:55:42     | all of that into fresh clone of master
14:56:06     | then did the usual rake generate_session_store
14:56:12     | rake db:migrate RAILS_ENV=production
14:56:16     | rake db:migrate:upgrade_plugin_migrations RAILS_ENV=production
14:56:20     | rake db:migrate_plugins RAILS_ENV=production
14:56:26     | rake tmp:cache:clear
14:56:27     | rake tmp:sessions:clear
14:56:30     | restarted apache

Updated by Eric Davis at 2011-02-26 11:32 pm

I've added documentation for upgrading ChiliProject and to Migrate From Redmine. Like I said in IRC, it looks like Redmine 1.1.1 and below are just a straight switch over to our git repo and then a db:migrate.

Redmine trunk and 1.2 will need some work since they include more database changes but they aren't yet released and we might pull in some of their code anyway.

P.S. I tested the upgrade with a Redmine 0.9, 1.0-stable, and 1.1-stable databases. My ChiliProject development database is also based on 1.0.5 and it was migrated cleanly a few weeks ago.

  • Status changed from Open to Closed

Also available in: Atom PDF