this largely depends on the version of ChiliProject you have currently running and the plugins you have installed.
I fear I can only show how to migrate a bare (without plugins) ChiliProject. With plugins involved you will first have to check on their compatibility with OpenProject. And as we just switched from rails 2.3 to rails 3.2 there will not be to many plugins out there right now that fit our altered plugin API. As we are going to release a whole lot of plugins in the near future that will change soon. But plugins you might have installed will have to be addressed individually regardless. If you have plugins installed, please let me know and I will try to figure out what to do with them as soon as possible.
The approach for a bare ChiliProject to OpenProject migration is basically as follows. This assumes that you have a ChiliProject v3.8.0 running:
Backup your DB or copy the DB over to a new one.
Double check that you have a backup of your DB.
Migrate your current database schema down to a version compatible to OpenProject.
Install OpenProject (including running the migrations).
Let me elaborate on this. Please note however, that I did not run those steps myself, as I currently do not have a ChiliProject installed.
OpenProject was forked from ChiliProject and as such shares most of the migrations. But some of the migrations are unique to ChiliProject and will now work when running an OpenProject. Those have to be removed using the following commands (shell in the rails root directory):
Once that is done, you can install OpenProject and use the DB you just prepared. You will first have to install the OpenProject version 2.4. OpenProject 2.4 is a necessary intermediate step as we squashed some migrations from 2.4 to 3.0. Feel free to switch to OpenProject 3.0 later. Right now OpenProject 3.0 is in a beta phase (so don’t use it for production yet) but should be stable soon.
Hope that helps. Please let me know if you have any additional questions. I would also like to have your feedback on this little write up in any case as this might be the starting point for a wiki page on the subject of migrating.
Replies (1)
Hey Ronny,
this largely depends on the version of ChiliProject you have currently running and the plugins you have installed.
I fear I can only show how to migrate a bare (without plugins) ChiliProject. With plugins involved you will first have to check on their compatibility with OpenProject. And as we just switched from rails 2.3 to rails 3.2 there will not be to many plugins out there right now that fit our altered plugin API. As we are going to release a whole lot of plugins in the near future that will change soon. But plugins you might have installed will have to be addressed individually regardless. If you have plugins installed, please let me know and I will try to figure out what to do with them as soon as possible.
The approach for a bare ChiliProject to OpenProject migration is basically as follows. This assumes that you have a ChiliProject v3.8.0 running:
Let me elaborate on this. Please note however, that I did not run those steps myself, as I currently do not have a ChiliProject installed.
OpenProject was forked from ChiliProject and as such shares most of the migrations. But some of the migrations are unique to ChiliProject and will now work when running an OpenProject. Those have to be removed using the following commands (shell in the rails root directory):
Once that is done, you can install OpenProject and use the DB you just prepared. You will first have to install the OpenProject version 2.4. OpenProject 2.4 is a necessary intermediate step as we squashed some migrations from 2.4 to 3.0. Feel free to switch to OpenProject 3.0 later. Right now OpenProject 3.0 is in a beta phase (so don’t use it for production yet) but should be stable soon.
Hope that helps. Please let me know if you have any additional questions. I would also like to have your feedback on this little write up in any case as this might be the starting point for a wiki page on the subject of migrating.
Best
Jens