Obsidian Stats

Stay informed about the Obsidian plugin ecosystem with Obsidian Stats! Whether you're tracking trending plugins, new releases, or your personal favorites, we've got you covered.

Features

Explore Obsidian plugins with these powerful features:

• New Plugins – Discover plugins released in the past 10 days.
• Latest Updates – Stay up to date with the latest releases and changelogs.
• Trending Plugins – Check out the top 10 trending plugins based on downloads and engagement.
• Most Downloaded – View the most downloaded plugins over last week, last month and overall timeline.
• Favorites – Track your favorite plugins and get notified of new updates.
• Plugin Sharing – Compare and share plugin lists with others.
• Migration Guide – Export and import your favorite plugin lists across devices.
• Scoring System – Build custom scoring functions to rank plugins based on your criteria.
• Tags – Browse plugins by tags to find exactly what you need.
• Share – Share your favorite plugin lists with the community.

Screenshots

Docker Deployment

Run Obsidian Stats in a Docker container with minimal image size (~50-100MB).

Prerequisites

• Docker installed on your system
• A .env file with required environment variables

Build the Docker Image

The Dockerfile accepts DATABASE_URL as a build argument, which is required for Prisma to generate the client during the build phase.

PowerShell (Windows):

docker build --build-arg DATABASE_URL="your_mongodb_connection_string" -t obsidian-plugins-stats .

Bash (Linux/Mac):

docker build --build-arg DATABASE_URL="your_mongodb_connection_string" -t obsidian-plugins-stats .

Load from .env file (PowerShell):

$DATABASE_URL = (Get-Content .env | Select-String -Pattern '^DATABASE_URL=').ToString().Split('=', 2)[1]
docker build --build-arg DATABASE_URL="$DATABASE_URL" -t obsidian-plugins-stats .

Run with Environment File

docker run -p 3000:3000 --env-file .env obsidian-plugins-stats

Using Docker Compose

For easier management, use Docker Compose:

docker-compose up -d

To stop the container:

docker-compose down

Environment Variables

Create a .env file in the project root with your configuration:

DATABASE_URL="your_database_url"
NEXT_PUBLIC_SUPABASE_URL="your_supabase_url"
NEXT_PUBLIC_SUPABASE_ANON_KEY="your_supabase_key"
# Add other required environment variables

Access the Application

Once running, access the application at http://localhost:3000

License

MIT

---

If you find this tool useful, consider supporting me with a coffee! ☕