🚨⚠️Users Moving from the old tracker, and those updating from 3.x to 4.x - please refer to the Database Migration Guide.⚠️🚨

Resource Tracker

A comprehensive resource management and tracking portal with Discord authentication and role-based access control. Perfect for gaming communities, organizations, and teams that need to track shared resources, inventory, or assets.

Made for Dune: Awakening. Originally forked from https://github.com/theyetty and adapted to the specific needs of my guild.

Removed from fork network due to original author repository being deleted, and database/backend changes incompatible with other forks.

---

[4.5.0] - 2026-05-01

Redesigned Resource Cards & Sparklines

✨ Features

• Redesigned Grid Cards: Completely overhauled resource grid cards for both desktop and mobile. The new layout features a status-keyed accent left border, inline status chips with colored indicator dots, large monospace quantity totals, and cleaner color-coded progress bars.
• Sparkline Trend Charts: Introduced dynamic, responsive sparklines to resource grid cards to visualize 30-day historical trends (powered by a new batch fetch endpoint). To preserve UI layout consistency, cards with insufficient data display a blurred, deterministic synthetic curve paired with a "NOT ENOUGH HISTORICAL DATA" overlay.

🚀 Improvements

• Consistent Tier Badging: Image thumbnails in the Table view now feature a tier pill overlaid on the corner to match the new grid card design.
• Enhanced Detail View: The primary image container on the Resource Details page has been updated to be larger (160×160 px), rounded, and includes the new corner tier pill overlay.

---

[4.4.1] - 2026-04-30

Security dependency updates

🚀 Improvements & Tech Debt

• Security Patches: Resolved CVE-2026-41305 (PostCSS XSS), GHSA-w5hq-g745-h8pq (uuid buffer bounds), and CVE-2026-33750 (brace-expansion ReDoS) via package overrides.
• Native Fetch API: Removed the node-fetch dev dependency in favor of the Node 22 native fetch API.

---

[4.4.0] - 2026-04-24

Sidebar Navigation & Improved Resource History Chart

✨ Features

• Sidebar Navigation: Replaced the top navigation bar with a collapsible sidebar on desktop and a slide-out drawer on mobile. The sidebar provides consistent navigation to Dashboard, Resources, Leaderboard, Activity, Settings, and Privacy from every page.

🚀 Improvements

• Enhanced History Chart: Improved the Resource Details quantity-over-time chart with a proper coordinate system (viewBox), dashed grid lines, Y-axis labels, X-axis date labels, a dashed target line, path-based series rendering, and a legend below the chart.
• Informative CSV Exports: CSV export now includes a read-only 'tier' column showing the human-readable tier/grade label (e.g. "Grade 4", "Tier 3 (Steel)") to help identify resources that share the same name but differ by grade. The column is ignored on import.

---

[4.3.0] - 2026-04-19

Dynamic Inventory Locations, Category Expansion, & Dependency Updates

✨ Features

• Custom Inventory Locations: Admins can now dynamically rename the two inventory locations via the Settings page (/dashboard/settings). The UI (tables, modals, and activity logs) now reads these location names from a shared React Context rather than using hardcoded values.
• Rapid Resource Templating: Admins can now duplicate an existing resource directly from its detail page using a pre-filled modal.
• Expanded Categories & Subcategories: * Renamed the legacy "Blueprints" category to "Gear Blueprints".
  • Added three new resource categories: "Gear", "Augmentations", and "Augmentation Blueprints", each complete with subcategory mapping.
• Expanded Resource Tiers: Renamed Tier 6 to "Tier 6/Grade 0 (Plastanium)" and introduced Graded support with Grade 1 through Grade 5 options (values 7–11).
• Agnostic Database Schema: Introduced quantityLocation1 and quantityLocation2 columns to the database schema to replace hardcoded "Hagga" and "Deep Desert" columns.
• Seamless API Fallbacks: All backend routing (resources, history, leaderboard, and activity) has been refactored to dual-read and dual-write across the legacy and new location schemas, ensuring a seamless, zero-downtime transition. Read operations dynamically fallback to legacy values if new columns are not yet populated.

🚀 Improvements & Tech Debt

• Automated Data Backfill: Implemented an idempotent background migration script (scripts/backfill-inventory-locations.ts) that runs automatically during the Vercel build pipeline to copy legacy inventory stock and history over to the new schema columns.
• TypeScript 6.0 Upgrade: Upgraded TypeScript to 6.0.2 and implemented types/vendor.d.ts for side-effect-only imports.
• ESLint 10.0 Upgrade: Upgraded ESLint to 10.1.0 and migrated eslint.config.mjs to utilize native flat config combined with @typescript-eslint/parser.
• Dependency Bumps: * Updated drizzle-orm to 0.45.2.
  • Updated lucide-react to 1.7.0 (swapping the deprecated Github icon for FaGithub).
  • Applied security patches for picomatch (2.3.2).

See lib/changelog.json for previous update history.

---

The main resource management grid.

Detailed view with activity timeline and contribution stats.

✨ Features

• Discord OAuth Authentication - Secure login with Discord.
• Role-Based Access Control - Granular permissions managed through your Discord server roles.
• Resource Management - Track quantities across two locations with visual status indicators.
• Activity Logging - Complete audit trail of all user actions with time filtering.
• GDPR Compliance - Tools for user data export and deletion.
• Grid & Table Views - Multiple layouts to view and manage resources.
• Interactive Charts - Visualize resource history with interactive data points.
• Gamification - A points-based leaderboard system to encourage contributions.
• Admin Controls - Full control over resources, targets, and user data for authorized roles.
• Responsive Design - Modern UI optimized for desktop and mobile devices.

---

🚀 Free Deployment Guide

This guide will walk you through deploying your own instance of the Resource Tracker for free using Vercel and Turso.

✅ Prerequisites

Before you start, make sure you have the following installed:

1. Node.js: Version 22.x LTS is required. You can download it from nodejs.org.
2. Git: Required for cloning the repository. Download it from git-scm.com.
3. A code editor: Such as VS Code.

Step 1: Fork and Clone the Repository

1. Fork the project: Click the "Fork" button at the top-right of this page to create your own copy.
2. Clone your fork: Open your terminal or command prompt and run the following command, replacing YOUR_USERNAME with your GitHub username:

   git clone https://github.com/YOUR_USERNAME/ResourceTracker.git
   cd ResourceTracker

Step 2: Set Up Discord OAuth

1. Navigate to the Discord Developer Portal and click "New Application".
2. Give your application a name (e.g., "My Guild's Resource Tracker").
3. Go to the "OAuth2" tab.
4. Copy the Client ID and Client Secret. You will need these later.
5. Under Redirects, add the following URL: http://localhost:3000/api/auth/callback/discord. We will update this with our production URL later.

Step 3: Get Discord Server Details

1. Enable Developer Mode in Discord: Go to User Settings > Advanced and turn on "Developer Mode".
2. Copy Server ID: Right-click your Discord server icon and select "Copy Server ID".
3. Copy Role IDs: In your server settings, go to Roles, right-click a role you want to configure, and select "Copy ID". You'll need at least one role for basic access. For more details, see the role configuration guide.

Step 4: Create a Free Turso Database

1. Sign up for a free account at turso.tech. The free tier is very generous.
2. Click "Create Database".
3. Choose a name (e.g., resource-tracker-db) and select the region closest to you.
4. Once created, copy the Database URL (starts with libsql://) and generate and copy an Auth Token.

Step 5: Initial Vercel Deployment

1. Go to vercel.com and sign up with your GitHub account.
2. Click "Add New... > Project" and import your forked repository.
3. In the "Configure Project" screen, expand the Environment Variables section. Add all variables from the table below, but leave NEXTAUTH_URL empty for now.

Variable Name	Value	Description
DISCORD_CLIENT_ID	From Step 2	Your Discord application's Client ID.
DISCORD_CLIENT_SECRET	From Step 2	Your Discord application's Client Secret.
DISCORD_GUILD_ID	From Step 3	Your Discord server's ID.
DISCORD_ROLES_CONFIG	See note below	Single-line JSON for role permissions. See ENVIRONMENT.md.
NEXTAUTH_URL	Leave this blank for now.	The production URL of your Vercel app.
NEXTAUTH_SECRET	Generate a secret	Run openssl rand -base64 32 in your terminal to create one.
TURSO_DATABASE_URL	From Step 4	Your Turso database URL.
TURSO_AUTH_TOKEN	From Step 4	Your Turso database authentication token.
NEXT_PUBLIC_ORG_NAME	Your choice	Your community or organization's name.

Important: For DISCORD_ROLES_CONFIG, the JSON must be on a single line. Start with a simple configuration for a single admin role: [{"id":"YOUR_ADMIN_ROLE_ID","name":"Admin","level":100,"isAdmin":true,"canAccessResources":true,"canEditTargets":true}]

4. Click Deploy.
5. Set Node.js Version: After the first deployment, go to your project's Settings > General on Vercel, set the Node.js Version to 22.x.

Step 6: Configure Production URL

1. Once the deployment is complete, go to your project's dashboard on Vercel and copy the primary domain (e.g., https://your-project.vercel.app).
2. Go back to your project's Settings > Environment Variables.
3. Add a new environment variable: NEXTAUTH_URL and paste the domain you just copied.
4. Redeploy: Go to the Deployments tab, click the latest deployment, and select "Redeploy" from the menu. This ensures the new NEXTAUTH_URL variable is applied.

Step 7: Initialize the Database

1. Install dependencies locally: From the local pronect folder that you cloned in Step 1:

   npm install

2. Create .env.local file: In your local project folder, create a file named .env.local and add your Turso credentials:

   TURSO_DATABASE_URL=your_turso_database_url
   TURSO_AUTH_TOKEN=your_turso_auth_token
   

3. Run the Database Migration: This command creates and sets up the database schema.

   # Applies all existing migrations to create the schema and logs them.
   npm run db:migrate

Step 8: Populate with Sample Data (Optional)

You can add some initial data to see how the application works.

# For Dune-specific resources
npm run populate-resources-dune

# For Tier-6 Blueprints
npm run populate-blueprints-dune

Step 9: Finalize Discord Configuration

1. Go back to the Discord Developer Portal and select your application.
2. In the "OAuth2" tab, under Redirects, add your production Vercel URL you configured in Step 6: https://your-app-name.vercel.app/api/auth/callback/discord

🎉 You're Done!

Your Resource Tracker is now live! Visit your Vercel URL to sign in with Discord.

---

🛠️ Local Development

For contributing or making customizations, follow these steps to run the project locally.

1. Install dependencies:

   npm install

2. Configure environment: Create a .env.local file in the root of your project. This file stores your secret keys and configuration for local development. Copy the example below and fill in your actual values.

   # .env.local
   
   # Discord OAuth (from your Discord Developer Application)
   DISCORD_CLIENT_ID=your_discord_client_id
   DISCORD_CLIENT_SECRET=your_discord_client_secret
   DISCORD_GUILD_ID=your_discord_server_id
   
   # Discord Roles (single-line JSON - see ENVIRONMENT.md for details)
   # Example with an Admin and a Member role:
   DISCORD_ROLES_CONFIG=[{"id":"1234567890","name":"Admin","level":100,"isAdmin":true,"canEditTargets":true,"canAccessResources":true},{"id":"0987654321","name":"Member","level":1,"isAdmin":false,"canEditTargets":false,"canAccessResources":true}]
   
   # NextAuth (generate secret with: openssl rand -base64 32)
   NEXTAUTH_URL=http://localhost:3000
   NEXTAUTH_SECRET=your_super_secret_key_generated_with_openssl
   
   # Turso Database (from your Turso dashboard)
   TURSO_DATABASE_URL=libsql://your-database.turso.io
   TURSO_AUTH_TOKEN=your_turso_auth_token
   
   # Optional: Customize branding for your local instance
   NEXT_PUBLIC_ORG_NAME=Dev Community

   For a detailed explanation of all variables, see ENVIRONMENT.md.

3. Set up the database:

   # Applies all existing migrations to create the schema and logs them.
   npm run db:migrate

4. Start the development server:

   npm run dev

   The app will be available at http://localhost:3000.

---

🎨 Customization

This application is designed to be easily customized:

• Branding: Set NEXT_PUBLIC_ORG_NAME for your organization's name.
• Roles: Configure permissions in DISCORD_ROLES_CONFIG.
• Resources: Modify the population scripts in the /scripts folder to fit your needs.
• Styling: Update colors and themes in tailwind.config.js and app/globals.css.

For more details, see the Customization Guide.

📚 Documentation

• ENVIRONMENT.md: Full guide to all environment variables.
• DB_MIGRATION.md: IMPORTANT guide for users upgrading from older versions.
• CONTRIBUTING.md: Guidelines for contributing to the project.
• docs/: In-depth documentation on architecture, API, and more.

🤝 Contributing

We welcome contributions! Please see CONTRIBUTING.md for guidelines on how to contribute to this project.

📄 License

This project is open source and available under the MIT License.