You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jrochkind edited this page Jan 3, 2012
·
12 revisions
There is no automated migration tool for moving from Umlaut 2.x to Umlaut 3.x.
You will just have to install Umlaut 3.x following the Installation instructions, and then re-apply your local customizations. This should hopefully not be too hard.
Some differences:
Umlaut is a gem now, your local Rails app is solely your own code, all shared Umlaut code is contained in the gem, not scattered about the rails app file structure.
The service configuration that was in ./config/umlaut_config/services.yml and institutions.yml is now combined in one file in ./config/umlaut_services.yml. In a slightly different form.
Configuration which before was recommended in initializers in ./config/umlaut_config/initializers now takes place in ./app/controllers/umlaut_controller.rb. The methods for adding configuration paramters have changed (we now use confstruct behind the scene), and some config key names have changed.
Umlaut 3.x should have a new database created for it, it has somewhat different schema than Umlaut 2.x, and you should not try to share databases.
One thing you WILL want to do before transitioning to Umlaut 3.x in production is move all your saved permalinks over to the new database, so permalinks created under Umlaut 2.x still work. We will have a script to do this before final release of umlaut 3.0.0. (Currently in dev, running into some tricks).