Closed hackartisan closed 7 years ago
The first level of stats setup is as simple as entering a google analytics ID in the sufia config file. Since this ID is made public through javascript, I assume this is safe to check in to the repo.
Once the google analytics ID is checked in, it will be linked to all dev instances, as well as staging and production. Do we want to think about impact of internal users on stats? Do we need to do tuning in GA to filter out urls like /dashboard/works
?
Regarding dev / staging / prod this may be a job for environment variables, or the environment-specific config files. The latter keeps us from having to touch deploy scripts.
Okay since we don't need alternatives on staging or dev, I'm just going to put this in for production only. Sorry for all the comments in a row.
Done on the application side; server-side piece written up for @sanfordd at https://3.basecamp.com/3311666/buckets/3817526/todos/532441493
https://github.com/projecthydra/sufia/wiki/Sufia-Management-Guide#analytics-and-usage-statistics