NBA Feed
Your teams' news and games, with scores hidden until you reveal them.
RunRush tracks your runs, boosts performance, and keeps you motivated — every step of the way.
Sports & fitnessHTML · PythonGitHub @Yajat-SharmaOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
🏃 RunRush — An AI-powered social running platform with analytics, streaks, badges, leaderboards, and offline-first tracking.
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
RunRush
Track. Improve. Repeat.
A modern, offline-first Progressive Web Application (PWA) for runners who mean business.
RunRush is more than a standard CRUD application—it is a production-minded, offline-capable fitness platform engineered for high performance and reliability.
Designed for runners who need their tools to work anywhere—even on a remote trail with zero cellular coverage—RunRush leverages a robust Progressive Web App (PWA) architecture to deliver a native-like experience directly in the browser.Read the full README ↗Screenshot files to supply: docs/assets/login.png, docs/assets/dashboard.png, and docs/assets/run-logging.png.
RunRush is an offline-first running tracker for logging runs, following progress, and sharing milestones. Its Progressive Web App architecture supports local run logging when the network is unavailable and synchronization when connectivity returns.
GradientBoostingRegressor is used when there is enough data; smaller histories use a weighted-average fallback.RunRush uses a service worker and IndexedDB so users can queue a run while offline and synchronize it when the connection returns.
flowchart TD
A[RunRush PWA] --> B{Network Available?}
B -->|Yes| C[Flask Backend]
B -->|No| D[(IndexedDB)]
D --> E[Offline Run Queue]
E --> F{Connection Restored?}
F -->|Yes| G[Sync Engine JS]
G -->|Hash validation and duplicate check| C
C --> H[(PostgreSQL / SQLite)]
H --> I[Dashboard UI]
flowchart LR
subgraph Client [Browser / PWA]
UI[Templates and JavaScript]
SW[Service Worker]
IDB[(IndexedDB)]
end
subgraph Server [Backend]
Flask[Flask Application]
Services[Application Services and AI]
ML[Run Prediction]
end
subgraph Data [Storage]
DB[(PostgreSQL or SQLite)]
end
UI <--> SW
SW -.-> IDB
SW <--> Flask
Flask <--> Services
Flask <--> ML
Flask <--> DB
| Layer | Technology |
|---|---|
| Backend | Python, Flask, Werkzeug, Jinja2 |
| Frontend | HTML5, CSS3, Vanilla JavaScript, Bootstrap |
| Database | PostgreSQL in production, SQLite for local development |
| Offline Storage | IndexedDB, Web Storage API |
| PWA | Web App Manifest, Service Worker Cache API |
| Data Visualization | Chart.js |
| ML | scikit-learn (GradientBoostingRegressor), pandas, NumPy |
| AI | Google Gemini API (google-genai) |
| Security | bcrypt, Flask-WTF/CSRF, Flask-Limiter |
| CI | GitHub Actions |
| Deployment | Gunicorn on Render |
RunRush/
├── .claude/launch.json
├── .env.example
├── .github/workflows/python-app.yml
├── .gitattributes
├── .gitignore
├── .python-version
├── LICENSE
├── pytest.ini
├── README.md
├── app.py
├── config.py
├── db.py
├── docs/
│ ├── archive/
│ │ ├── RUNRUSH_CODEBASE_AUDIT.md
│ │ ├── RunRush_Project_Report.html
│ │ ├── STEP4_INVESTIGATION.md
│ │ ├── database-compatibility-audit.md
│ │ ├── database-migration-map.md
│ │ └── improvements-history.md
│ ├── assets/
│ │ └── .gitkeep
│ ├── deployment.md
│ ├── developer-guide.md
│ └── project-summary.md
├── extensions.py
├── gunicorn.conf.py
├── marketing/
│ ├── runrush-qr-card.png
│ ├── runrush-qr.png
│ └── runrush-qr.svg
├── migrations/
│ ├── 001_initial_schema.sql
│ ├── 002_seed_badges_challenges.sql
│ ├── 003_add_user_onboarding_fields.sql
│ ├── 004_add_monthly_goals.sql
│ ├── 005_add_profile_emoji.sql
│ ├── 006_add_notifications.sql
│ ├── 007_add_monthly_summary_deliveries.sql
│ ├── 008_add_run_likes.sql
│ ├── 009_drop_user_pets.sql
│ └── README.md
├── ml_predictor.py
├── models/
│ ├── __init__.py
│ └── user.py
├── requirements-dev.txt
├── requirements.txt
├── schema.sql
├── scripts/
│ ├── add_dummies.py
│ ├── apply_migration_006.py
│ ├── apply_migration_008.py
│ ├── apply_migration_009.py
│ ├── delete_user.py
│ ├── migrate_to_pg.py
│ └── smoke_script.py
├── services/
├── static/
│ ├── css/
│ ├── fonts/
│ ├── icons/
│ ├── img/
│ ├── js/
│ ├── manifest.json
│ └── sw.js
├── templates/
├── tests/
└── utils/
├── __init__.py
├── dates.py
├── decorators.py
├── rate_limiter.py
└── validators.py
RunRush uses SQLite for local development.
git clone https://github.com/Yajat-Sharma/Runrush.git
cd Runrush
python -m venv .venv
# Windows: .venv\Scripts\activate
# macOS/Linux:
source .venv/bin/activate
pip install -r requirements-dev.txt
Copy .env.example to .env and set the required local values, including a SECRET_KEY. Then start the app:
python app.py
The development server is available at http://localhost:5000.
See the Render deployment guide for service settings, database configuration, and the SQLite-to-PostgreSQL migration command.
Contributions are welcome. Fork the repository, create a feature branch, commit your changes, and open a pull request.