figure out correct settings for assets in production deployment

[annakrohn]

In order to get the production environment to work, I've had to disable the asset caching and precompile. But we should be using this for deployment so we need to figure what the correct settings are to make this work in the production environment.

There were a number of problems with the caching.

The most crucial was with the config.cache_classes=true setting, which should be set in a production environment as it eliminates the need to recompile the ruby code with each request. This was failing because we had a 2nd blacklight controller, the VisController, which caused the blacklight application initialize method to be called twice, which resulted in the solr config settings being duplicated (and failing). Removing the VisController class (which wasn't being used at this point as it was for testing visualizations) resolved this problem and we can now set config.cache_classes=true in the production.rb

We still have issues with the assets settings though:

1. we should probably precompile the assets at deploy time, so that we can set config.assets.compile=false and config.assets.compress=true. I think it might just be as simple as calling rake assets:precompile but there might be more to it

2. for some reason, if config.assets.debug=false, it seems like some or all of the jQuery handlers aren't being called. This manifests itself, for example, in the expansion handlers for the edition/translation/version lists for a work -- these sections just show up expanded by default with no ability to click on them.

I don't think these latter two issues are crucial for release - for now I've just set config.assets.compile=true and config.assets.debug=true in the production.rb. However, I think we ought to investigate and resolve this after the initial release, so I'm going to reassign this item to Anna and target it to Release 1.1

Mantis http://bugs.perseus.tufts.edu/view.php?id=1170