-
Notifications
You must be signed in to change notification settings - Fork 553
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
INIT: Analytics to CLI Installer #4088
Comments
we should use the same proxy we are using to share the analytics from CLI, for we don't expose the token into the script. Because if we do |
When the script is called, we should make an HTTP request to Google Analytics, passing the version of the Ignite into the request, like the CLI is doing: Lines 80 to 113 in 9a233e6
The analytics should be sent at the end of the script and not fail in case the request fails. |
Do note that installation on snap or homebrew won't be counted.
Should we really keep promoting the manual install when we have package managers? |
Can we track these installations @julienrbrt ? |
Those are both tracked yes. I can add you to the monthly emails for snaps if you want. |
We can get the brew analytics from the API. Can we easily collect this data to add to the analytics? https://formulae.brew.sh/api/formula/ignite.json {
"analytics": {
"install": {
"30d": {
"ignite": 76
},
"90d": {
"ignite": 275
},
"365d": {
"ignite": 275
}
},
"install_on_request": {
"30d": {
"ignite": 76
},
"90d": {
"ignite": 275
},
"365d": {
"ignite": 275
}
},
"build_error": {
"30d": {
"ignite": 0
}
}
}
} |
We have this installer to install the ignite binary thoughts curl (
curl https://get.ignite.com/cli! | bash
). We need to add analytics to it to track the number of downloads and which version.The text was updated successfully, but these errors were encountered: