WaterTrack has no build step, no server, and no package manager — getting it running takes only as long as it takes to move four files into place. This guide walks through three paths: running the app locally straight from the file system, deploying it for free on GitHub Pages, and self-hosting it on any static file server of your choice.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/mr-sunset/watertracker/llms.txt
Use this file to discover all available pages before exploring further.
Run Locally
The fastest way to use WaterTrack is to clone the repository and openindex.html directly in your browser. Because the app is built with plain HTML, CSS, and vanilla JavaScript, no local server or compilation is required.
Clone the repository
Run the following command in your terminal to download the project files:This creates a
watertracker/ directory containing index.html, script.js, style.css, and favicon.png.Open index.html in your browser
Navigate into the cloned directory and open You can also drag and drop
index.html directly — no build step, no npm install, no local server needed:index.html onto any open browser window or tab.Deploy to GitHub Pages
GitHub Pages lets you host WaterTrack for free at a public URL so you can reach it from any device without self-hosting infrastructure.Fork the repository on GitHub
Visit the WaterTrack repository on GitHub and click Fork in the top-right corner. This creates your own copy of the repo under your GitHub account.
Enable GitHub Pages in repository settings
In your forked repository, go to Settings → Pages (under the Code and automation section). Under Source, select Deploy from a branch, choose the
main branch, and set the folder to / (root). Click Save.Self-Host on a Static File Server
If you already have a server or a hosting platform, deploying WaterTrack is as simple as copying four files.Copy the project files to your server
Upload or copy the following four files to your web root (or a subdirectory of your choice):These are the only files the app needs. There is no
dist/ folder to build.Serve the files with any static file server
WaterTrack works with any server or platform that can serve static files, including:
- nginx or Apache — point the document root at the directory containing
index.html - Caddy — a one-line
file_serverdirective is all that’s needed - Netlify or Vercel — drag-and-drop the folder in their dashboards or push to a connected Git repo
- Any shared hosting — FTP the files and you’re done
WaterTrack has no back-end, database, or build pipeline. The only external dependency is the confetti script loaded from the jsDelivr CDN (
https://cdn.jsdelivr.net/npm/@hiseb/confetti@2.1.0/dist/confetti.min.js). If you need to work fully offline or in an environment that blocks CDN requests, the confetti effect won’t fire — but every other feature, including drink logging and localStorage persistence, works perfectly without it.