feat: Add visit counter with geolocation #3
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit introduces a feature to track visits for each redirected domain, including geolocation information based on the visitor's IP address. A SQLite database (`stats.db`) is used to persistently store visit data. Each visit records the URL, a timestamp, and the visitor's country and city. The geolocation is performed by calling the `ip-api.com` external service. While a local database like GeoLite2 was initially considered, the external API is simpler to integrate for this project's scale. A new API endpoint `/stats` is added to expose the collected data. It returns a JSON response with the total number of visits, a breakdown by URL, and for each URL, a breakdown by country. It also includes a simple metric for "unique users today," which is based on a count of distinct cities. The previous in-memory visit counter has been removed. A `.gitignore` file has also been added to exclude build artifacts and the database file from version control.
This commit fixes the Docker build by enabling cgo, which is required by the `go-sqlite3` driver. The `golang:alpine` base image does not have cgo enabled by default. This change adds the necessary build tools (`gcc`, `musl-dev`) to the builder stage and sets `CGO_ENABLED=1` during the `go build` command. This ensures that the application can correctly link against the C-based SQLite library when built inside the Docker container.
This commit addresses two issues: 1. The visit counter was incorrectly incrementing for any visited path. The main handler has been modified to only process requests for the root path (`/`), ensuring that only relevant visits are counted. 2. The database was not persistent when running in Docker. The application now uses the `DB_PATH` environment variable to allow specifying a custom path for the database file. The `README.md` has been updated with instructions on how to use this with Docker volumes to achieve data persistence.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit introduces a feature to track visits for each redirected domain, including geolocation information based on the visitor's IP address.
A SQLite database (
stats.db) is used to persistently store visit data. Each visit records the URL, a timestamp, and the visitor's country and city.The geolocation is performed by calling the
ip-api.comexternal service. While a local database like GeoLite2 was initially considered, the external API is simpler to integrate for this project's scale.A new API endpoint
/statsis added to expose the collected data. It returns a JSON response with the total number of visits, a breakdown by URL, and for each URL, a breakdown by country. It also includes a simple metric for "unique users today," which is based on a count of distinct cities.The previous in-memory visit counter has been removed. A
.gitignorefile has also been added to exclude build artifacts and the database file from version control.