78436b230b
- Moved notes-related routes (viewing/editing workout notes) from `app.py` into a new blueprint at `routes/notes.py`. - Integrated notes-specific database logic (fetching and updating notes) directly into `routes/notes.py` helper functions, removing the corresponding methods from `db.py` for better encapsulation. - Registered the new `notes_bp` blueprint in `app.py`. - Removed the original notes route definitions from `app.py`. - Updated `url_for` calls in `templates/partials/workout_note.html` to reference the new blueprint endpoints (e.g., `notes.get_person_notes`). - Updated `templates/changelog/changelog.html` to document this refactoring in its own entry.
Workout tracker
Track topsets over time.
Setup
Install python>3
Install dependencies
$ pip install -r requirements.txt
Enable development mode
PS $ENV:FLASK_ENV='development'
Set database url, either setup postgres database locally use migration script or expose deployed one
$Env:DATABASE_URL = 'postgres://postgres:***@***:***/***'
Start application:
flask run
Features
- Track topsets for each workout
- Multi user
- Authentication/Authorisation