Closed ehmatthes closed 2 years ago
Initial thinking was that this would be useful information to help convince Heroku to adopt an approach similar to this. But they can scan projects and count how many projects have been set to use this buildpack. So the only real reason to do this would be for my own information. That's still a really valuable piece of information as far as knowing if this project is meaningful or not.
https://api.github.com/repos/ehmatthes/heroku-buildpack-python/traffic/clones
curl username:access_token https://api.github.com/repos/ehmatthes/heroku-buildpack-python/traffic/clones
workscurl -u username:access_token https://api.github.com/repos/ehmatthes/heroku-buildpack-python/traffic/popular/paths
Could I make a dummy page in this repository, and "visit" that page through a curl call? That might show up in traffic, and would be specific enough to get some sense of usage.
I believe each deployment shows up as a clone. I cloned manually twice on Friday, and deployed test projects a number of times. There are 7 clones listed for Friday.
This is limited to the last 14 days, but that's plenty to see if the project is being used beyond test cases.
Currently, I have no real idea how many times this deployment process has been used. I do not want to track individual users or projects. I would like a simple count of how many times this has been used.
DISABLE_AUTOCONFIGURE_REPORTING
env var that turns this feature off.