DevOps Zone is brought to you in partnership with:

I am the API Evangelist. Not in the sense that I’m evangelizing a single API to you--In the sense that APIs are important for everyone to be aware of. I’m paying attention to not just the technical, but the business and politics of the web API movement. I share my insights by blogging on the business of APIs at apievangelist.com, politics of APIs at apivoice.com and you can find more information about me at kinlane.com. Kin is a DZone MVB and is not an employee of DZone and has posted 95 posts at DZone. You can read more from them at their website. View Full User Profile

Continuing the Migration of Projects Over to Github

03.23.2013
| 2694 views |
  • submit to reddit

I’m continuing the migration of all my projects to run on Github. Eventually all public areas of my site will run as static, published Github pages and supporting back-end repositories. Last night I migrated API aggregationBackend as a ServiceReciprocity and Real-Time providers using a version of my Hacker Storytelling format.

While apievangelist.com will still remain the master doorway to all my work, each project will live under its own subdomain and Github repository. As I make this switch I’m having to adjust my Google Analytics strategy as well as potentially my Google Feedburner strategy. In the shadow of the Google Reader deprecation I’m reconsidering not just how I consume RSS, but my analytics as well.

I can keep using Google Analytics for pages, and Google Feedburner for RSS. But I’d also like data on how JSON files are consumed as well, which neither platform provide me. Using the Github API I can track on the activity around a repository like commits, follows, downloads and forks, but I don’t get actually page view activity on pages or individual files.

Really my only hope for getting the data I need is from Github. Some sort of raw web logs for our domain, would be sweeeet!! Then I could see how many times a JSON file is accessed, and build custom reporting tools for Github page views, Jekyll blog views, etc and migrate away from Google Analytics.

I've looked briefly for any Github solutions, but everything is client-side tracking.  Let me know if I'm missing anything.

Published at DZone with permission of Kin Lane, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)