@@ -1,8 +1,9 @@ = WoopraAnalytics == Install gems -# gem sources -a http://gems.github.com -# sudo gem install jonathannelson-woopra_analytics + +=== gem sources -a http://gems.github.com +=== sudo gem install jonathannelson-woopra_analytics This module will easily enable Woopra Analytics support for your application. By default it'll output the analytics code for every single page automatically, if it's configured correctly. @@ -26,7 +27,7 @@ Use the following rake task to update the local copy of the JavaScript file: rake woopra_analytics:updates -===Keep in sync with your Capistrano deploys +=== Keep in sync with your Capistrano deploys To keep the file updated you can add the following to your Capistrano configuration: after "deploy:symlink", "deploy:woopra_analytics" @@ -40,7 +41,7 @@ To keep the file updated you can add the following to your Capistrano configurat The above Capistrano recipe will almost certainly need some adjustments based on how you run your deployments, but you should get the idea. -==Overriding Application-Wide Values +== Overriding Application-Wide Values If you're using one Rails application to serve pages across multiple domains, you may wish to override the domain and tracker ID values on a controller-by-controller or view-by-view basis. You can do this by setting the override_domain_name properties. These properties are automatically reset after each use, so the values you set for domain_name (usually in an initializer) will apply to all other requests. before_filter :local_analytics README.rdoc 87d0df513baddd3d4b4457a2223ba3e7453b539f jonathannelson jonathannelson@yahoo.com http://github.com/jonathannelson/woopra_analytics/commit/f00517e807d8dd93870c7aa184773d8be5329862 f00517e807d8dd93870c7aa184773d8be5329862 2008-11-02T08:02:58-08:00 2008-11-02T08:02:58-08:00 85fe0b2d422b3b7825efbd5085a5dbb5043bd9f2 jonathannelson jonathannelson@yahoo.com