While most configuration is done directly on cards...

• Sharking

  help edit space_dashboard

  Sharking is the process of creating, configuring, structuring, and evolving Decko websites.

   

  To get started as a Shark you really only need to tackle one concept: cards.

  cards

  more_horiz

  open_in_full page

  fullscreen modal

  edit edit

  space_dashboard advanced

  Design

• Security Configuration

  help edit space_dashboard

  If you're going to let unregistered users add/edit/comment on cards, we recommend that you use captcha.

...a few kinds of configuration require access to server files:

• Mail Configuration

  help edit space_dashboard

  Wagn's mailer setup inherits directly from rails and is configurable in config/application.rb (in Wagn 1.12.6 and later).   See the rails documentation on mailer configuration here:

   

  http://guides.rubyonrails.org/configuring.html#configuring-action-mailer 

• Image Issues

  help edit space_dashboard

  When all is working properly, Wagn stores several versions of an image: icon, small, medium, large, and full.  The preview you see upon uploading an image is the medium size; if that image is broken, there's a good chance that either (a) the image is not getting stored, or (b) the resizing is not happening.

   

  To investigate, look in the directory where the images are stored.  By default, this is public/card_images/0000/####/.

   

  If there are no images stored there at all, make sure the permissions are correct on the directory (the user running the server needs write permissions).

   

  If there is only the original image, with no resized versions, you probably have an issue with your resizing gem.  As of Wagn 1.6, Wagn is now explicitly requiring the image_science gem, whereas previously you could also use rmagick.  You can still get rmagick working by editing the Gemfile, but this installation is generally considerably more complicated.

   

  If both the image_science gem and the ruby_inline gem on which it depends are correctly installed, odds are that your issue with freeimage, the other (non-gem) library on which image_science depends.  We hope to include more detail about installing freeimage here soon, but in the meantime, we hope that this will be enough of a lead for you to find the solution.

   

  This command has been useful in getting freeimage working on machines running debian linux and derivatives:

   

  sudo aptitude install libfreeimage3 libfreeimage3-dev