Wagn 1.9+Blog
If you've been following Wagn, you know how excited we are about Wagn 2.0: how it will complete our transition from a nifty app to a powerful platform... how it will be easy to discover, use, and extend...
Well, we're getting closer! I should say up front: 1.9 will not be the last release before 2.0. We're planning 1.10 and 1.11 releases, as outlined on our roadmap.
That said,Wagn 1.9 takes some big steps.
One key step is that we've considerably increased the number of cards that can be renamed without creating problems by giving them an additional "codename" identifier to be used when referenced in the code. This is important for Wagn because we give so much power to Wagneers, who are essentially coding by manipulating card content. Our new, more robust approach allows for powerful relationships between code and content, so that we can continue to give Wagneers more and more new capacities.
1.9 is also slimmer. By moving data into cards, we've gone from having seven core data tables to having just four. (We'll be down to three in 1.10). This has considerably simplified our codebase without sacrificing any functionality.
Perhaps most importantly, it gets us much closer to the 2.0 apis (both REST and pack) that we think will make Wagn the platform of the future.
See the Release card for tickets and update details.
Standard Upgrade
1. Backups
Always back up your database and uploaded files.
2. Update Libraries
From your decko root directory run:
bundle update3. Update Database
Run the following:
decko update4. Restart your server.
Upgrade to Decko from Wagn
1. update references to “wagn” in file content
In your decko's root directory, edit Gemfile, config/application.rb, and config/routes.rb, and script/wagn, replacing “wagn” with “decko”. (Keep the same capitalization pattern.)
2. update references to “wagn” in file names.
From your decko root directory run:
mv script/wagn script/decko3. continue as with Standard Upgrade
See above.
If your Wagn was NOT installed from a gem, then first check the Wagn version of your existing installation:
For version 1.10 through 1.12.6
- Create a new Wagn app using steps 1 and 2 from the installation section above.
- Copy config/database.yml from the old site to the new one.
- Copy the old local/files contents to the new files directory.
- If you have edited config/wagn.yml in your old site, make the corresponding changes to the new config/application.rb file.
- Follow the standard upgrade procedure above.
Upgrading pre-version 1.10
First update your Wagn to version 1.10 via the old update mechanisms, and then follow the directions above to then upgrade to the wagn gem.
- if you have written custom modules, you will need to make sure that all card names used in view identifiers are using "codenames".
Wagn 1.9+tickets by status
open
in progress
coded
testing
closed
Wagn 1.9+Documentation Ticket
migrate away all old global permissions links?
--Ethan McCutchen.....2012-10-01 16:33:44 +0000
(not migrating those yet. for now they go to a deprecation notice)
--Ethan McCutchen.....2012-10-09 21:38:42 +0000