Stars are not downloads
A publicDockerfile or docker-compose.yml is easy to share and hard to measure. GitHub can show stars and clones. It does not show that a developer copied the curl line from your docs, a conference slide, or a blog post and actually fetched the file.
Put a short link in front of the raw file. The download still works. You get a count.
The command people copy
Point the short link at the raw file URL. Replace the long address in the README, the docs, and any tutorial.# Before
curl -L https://raw.githubusercontent.com/user/repo/main/docker-compose.yml
# After
curl -L https://viso.li/my-docker-config
curl -L follows the redirect, so the file still lands on disk. The shortener records the request on the way through: visits, unique visitors, location, referrer, and timing.
Use a different short link in each place you publish the command if you need to know which one was copied:
viso.li/compose-readmein the GitHub READMEviso.li/compose-docson the documentation siteviso.li/compose-talkon the slide or the blog
What you can learn, and what you cannot
You can learn when the file was fetched, which country the requests came from, and which page referred them. That is enough to see whether a launch post worked, and whether a region you do not support is fetching the file anyway. You cannot turn that into a list of company names. The click is anonymous. A busy country is a hint about where to write the next doc or run the next office hours. It is not a lead list. If a script fetches the file on a timer, those repeats show up as visits. Unique visitors are the fairer count of people. Say which number you mean.When the file moves
You can change the destination behind the short link when the path in the repo changes. Anyone who saved the curl command still gets the file. Mention the new path in the README, and keep the short link stable. For a tool you want developers to create links from inside a script, the link shortener API is the next step. For a human copying a command, the short link in the docs is enough.A README change
- Create a short link to the raw file.
- Put it in the install snippet at the top of the README.
- Use a second link if the docs site should be counted apart from GitHub.
- After the next announcement, compare visits on those links with the week before.

