If you're already at Wagn 1.13, this should be a pretty standard upgrade. However, do expect the migration to take a while; it's doing a lot of work restructuring the entire revisions table!
If you're not already at Wagn 1.13, have a look at this before proceeding:
Wagn 1.13 is Wagn's first minor release in the form of a ruby gem.
If you are upgrading from a site that is not already using the Wagn gem, then you will need to upgrade to the Wagn gem before following the new standard upgrade procedure or the notes below.
If you are upgrading from a pre-1.13 version using the Wagn gem, there are several things to keep in mind:
- Make sure you are in the folder where your Wagn web site is located (usually 'cd /var/www/your_wagn_website' will do)
- Wagn 1.13 moves all javascript into cards, which means you'll need an Execjs. If you're using a mac, then no worries; it's already built-in. Otherwise, you need to add this line to your Gemfile:
gem 'therubyracer'- You should no longer have to run `rake wagn:migrate`. The main command is now:
wagn updatewhich runs the migrations in additions to some other helpful commands. See the Updating card for more details.- If you're running wagn in production, you may have been running a symlink from your deck's "public" directory to the one in the gem directory. This symlink is no longer needed and should be removed. However, you can still improve performance of certain requests with a similar symlink to public/assets. This symlink is automatically generated when you run `wagn update` and can be generated directly (with no other side effects) by running `rake wagn:update_assets_symlink`.
- If you were using any mods, you may need to singularize some directory names. For example:
mods/mymod/sets/right/address.rbwould becomemod/mymod/set/right/address.rb- If you're interested in developing Wagn mods or the Wagn core, please contact us directly. Wagn 1.13 adds a lot more support there, but the documentation is lagging!