Add Self-hosted Umami analytics setup#356
Open
synan-mannan wants to merge 1 commit into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This pull request adds a complete setup guide for self-hosted Umami analytics.
It includes detailed instructions for environment variables, Docker deployment, PostgreSQL configuration, dashboard access, and website tracking.
The README has been enhanced to provide a step-by-step guide, making it easier for contributors or the organization to deploy Umami for privacy-first analytics.
Related Issue
References Issue: Set up analytics tracking tool #114
Motivation and Context
The project lacked a documented setup for self-hosted analytics, which is essential for tracking user behavior and traffic without relying on third-party services.
This enhancement ensures the organization can deploy Umami quickly, maintain visitor privacy, and have complete control over the analytics data.
It improves documentation quality, reduces setup errors, and makes contribution easier for new developers.
How Has This Been Tested?
Screenshots or GIF (In case of UI changes):
Types of changes
Checklist:
! Note: I added new documentation describing the analytics setup; existing docs were not modified, but documentation coverage was extended.