Hi Björn,

I have a migration guide as a work in progress. You’re right, we need Node.js and bower.

Here is the link to the guide: https://community.openproject.org/projects/openproject/wiki/OP3_to_OP4_Debian_upgrade

We’re currently collecting feedback,are looking for spelling mistakes, wierd grammar etc.
In parallel I am in the process of testing the guide step by step on a Debian VM so that I can be sure things work.

If you have any feedback, you are more than welcome to contact me!

cheers,
tessi

Ok..

A bit of feedback on the migration guide:

1. I would suggest that users make their own git branch for their local changes. Commit their local changes to their own branch. Then switch to stable, pull latest changes then switch back to their own branch and merge. (On the other hand with this approach, they will be required to solve any merge conflicts, which of course can be a hassle).

2. About Serving OpenProject. Do we really need this in a migration guide? Shouldn’t this part already be in place if the user is running OpenProject 3.0.x?

3. There are nothing in the aftermath stage of migration guide about starting the (apache) server again. (May be obvious but I think it should be mentioned since we explicitly close it during the preparation stage).

Regards
Björn

Thanks for having a look at the guide,

1. git branch vs. git reset
   I think you are right in principle. However, I’m not sure how complicated the guide is allowed to be. Often we get support queries with the simplest questions. Thus, I want to make the guide as simple and resistant to potential errors as possible. I hope, that anyone with some background knowledge is able to adapt the guide to his/her specific setup.
2. Serving OpenProject
   You’re right. We already describe how to serve OpenProject in the 3.0 installation guide. However, the ruby version is possible upgraded (from 2.1.0 in the 3.0 guide to 2.1.4 in the 4.0 guide).
   Also the passenger gem might be upgraded. Both versiosn (ruby and passenger) appear in the apache config. Thus, the config needs to be adapted somehow.
3. starting the server again
   Right! I’ll add this

The Serving OpenProject-part probably needs some refinements.
I’m going to make this part better as soon as my test-VM is at this step and I can get actual data/passenger-output.

Unfortunately my test-VM is so unbelievably slow, that it might take some time till I get there.

I have revised the “serving openproject” part to explain why we want to touch the apache config.

I hit a rather cumbersome problem.

bower openproject-ui_components#with-bower                                    ECMDERR Failed to execute "git ls-remote --tags --heads git://github.com/opf/openproject-ui_components.git", exit code of #128

Additional error details:
fatal: unable to connect to github.com:
github.com[0: 192.30.252.131]: errno=Connection refused

npm ERR! OpenProject@0.1.0 postinstall: `./node_modules/bower/bin/bower install`

npm install failed due to our server being behind a firewall. So I had to force bower to use https:// instead of git:// with:

git config --global url."https://".insteadOf git://

Many thanks for reporting the problem and, instantaneously, the solution. I’ve added your post to the FAQ of the upgrade and installation guide.

Regarding the plug-ins. Are these migrated recursively with the call to:

RAILS_ENV="production" bundle exec rake db:migrate

Or do they need separate migrate calls for each plug-in?

Hi Björn,

this command will also migrate the plugins. The same applies for db:seed and assets:precompile as well.

Best
Ratzi

Hi,

I'm trying to migrate a very old installation, i.e. 3.0.13, to the latest version. I was, obviously, trying to go stepwise, i.e. 3->4, 5->6, 6->7, 7->8 and then jump to 10.

Unfortunately, it's impossible to find old migration guides from v3. I was able to dig out older guides that start with version 4. The above link to the 3->4 guide leads to a 403 error. 

Any chance I could get access (or a PDF, whatever) to this document?

Hi David,

I attached you the old Upgrade guide. We squashed migrations two times in the past. At version 3.0 (you're past that already), and in version 7.1.:

https://github.com/opf/openproject/blob/dev/db/migrate/10000000000000_to_v710_aggregated_migrations.rb#L114-L115

In theory, you should be able to upgrade to v7.1.0, and afterwards to v10.6.1 (the current version). Whether that really works, I cannot tell you but we're very eager to find out how the upgrade process works for such an old version. I will send you a mail to reply to me directly so we can help you get it migrated - and ideally create a solid migration guide for legacy versions.

Best

Oliver

Wiki___OP3_to_OP4_Debian_upgrade___OpenProject_Community.pdf