Wagn administration includes maintaining an installation of Wagn on a server, and tasks within a Wagn generally managed by people with the Administrator role.

The Administrator links card is a good place to add information and links and information. Only Administrators can see it by default.

Also see:

• Configuration
• Accounts
• Permissions
• If you code at all, there's a lot of power in Script and Ruby cards.
• ...and feel free to ask for support.

Clearing the cache

Problems with the cache can result in people seeing different content on the same from different accounts, or even seeing different content from the same account at different times. To clear the cache, go to:

(your Wagn's base URL)/admin/clear_cache

Spam

captcha can protect against most non-human spam.

 

If you get an overwhelming number of obviously spammy Account Requests, you show them all in open view and thus easily deny them all with a link like this: http://wagn/org/Account_Request+*type+by_update?item=open

Upgrading

 

1. Back up your database!
2. Enter your wagn root directory
   By default this is named "wagn".  It should have directories named "app", "config", "lib", etc.
3. Update your source
   If you're using git, then go into the wagn directory and type:

   git pull
   # if that doesn't work try:
   git pull git://github.com/wagn/wagn.git
   # or
   git pull git://github.com/wagn/wagn.git master

4. Update your libraries
   

   bundle install

   For more info see using bundler with wagn.

5. Migrate your database
   

   rake db:migrate

   You may encounter issues if your wagn is badly out of date.  If so, we recommend that you do incremental upgrades by updating to each major release.  For example, if you encounter issues migrating from 1.5.4 to 1.8.1, try updating first to 1.6, then to 1.7, then to 1.8.1.

6. Clear your cache
   

   rake cache:clear

7. Restart your server
   If you are using the default (built-in) webrick server, you can now start your server with

   env STATIC_ASSETS=true rails server.

 

Tickets related to administering Wagn

Development Tickets (by status)

move cue text to editable cards

implement blacklisting

add content to account request emails

implement operations on groups of cards

expose deck metadata in cards

respect inclusions in star-invite-plus-star-subject

facilitate creation or import of multiple users

expose card metadata in cards

Site skin card

 

Ideas

expose date of deck's deploy

allow access to other files and CGIs on the server

Code cardtype - modular plugins

disentangle admin cards from coded cards

automatically generate sitemap

show IP for anonymous edits on recent changes

add a card for robots.txt

use image card for background image

 

Documentation Tickets

 

Support Tickets

Home link goes to admin-slash-setup

 

administration+anything closed tagged with    

...

administration+relevant user stories    

...

Notes