wagn in production

As of Wagn 1.8, wagn defaults to running in "production" mode.  We've chosen this Ruby-on-Rails mode to serve the many users who just want to use Wagn.  If you're someone who wants to help build wagn, please see wagn in development.

The default installation instructions will tell you how to get Wagn working with Rails' built-in webserver, Webrick.  Webrick is great for kicking the Wagn wheels, but not ideal for a production server.

To set up wagn behind an Apache webserver, we strongly recommend:

1. Phusion Passenger, aka mod_rails or mod_rack. Simplifies deploying rails applications.  (Examples coming soon.  For now, keywords: PassengerAppRoot, RackBaseURI)
2. mod_expires. Makes use of wagn's non-expiring assets so images, stylesheets, and javascript don't slow down page loads at all.
   
   This rake command will give you some needed htaccess files:

   rake wagn:copy_htaccess

3. You'll need to enable mod_headers so that the ht_access will work (Headers directives)
4. mod_xsendfile. File and Image cards process permissions before sending the file.  This makes that fast.
5. memcache. Fast caching.
   
   To configure wagn for memcache, edit config/wagn.yml with the following:
   

   cache_store: mem_cache_store
   # optionally:
   memcache_servers:
   - server1.com
   - server2.com

If you're using mysql, we recommend using the mysql2 adapter in database.yml.  As of 1.8, this adapter is causing problems in the initial database creation, so we're not ready to make it the default adapter, but we have not yet had any problems in a production environment.