Peter Stockings a8fe28339b I have refactored the SQL Explorer functionality into its own blueprint (routes/sql_explorer.py) with a /sql URL prefix. This involved moving the relevant routes from app.py, registering the new blueprint, removing the old routes, updating url_for calls in the templates, and documenting the change in the changelog.
Here is a conventional commit message summarizing the changes:

```
feat: Refactor SQL Explorer into blueprint

- Moved SQL Explorer routes (view explorer, save/load/execute/delete queries, view schema, plot queries) from `app.py` into a new blueprint at `routes/sql_explorer.py`.
- Added `/sql` URL prefix to the blueprint.
- Registered the new `sql_explorer_bp` blueprint in `app.py`.
- Removed the original SQL Explorer route definitions from `app.py`.
- Updated `url_for` calls in relevant templates (`sql_explorer.html`, `partials/sql_explorer/sql_query.html`, `base.html`) to reference the new blueprint endpoints (e.g., `sql_explorer.sql_explorer`).
- Updated `templates/changelog/changelog.html` to document this refactoring.
```
2025-03-31 23:00:54 +11:00
2025-02-01 21:26:52 +11:00
2022-07-15 21:06:27 +10:00
2022-09-17 16:42:50 +10:00
2022-09-10 15:09:17 +10:00
2022-09-17 13:38:41 +10:00

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
Description
No description provided
Readme 4 MiB
Languages
HTML 43.9%
Python 35.5%
Jupyter Notebook 18.8%
PLpgSQL 1.2%
CSS 0.6%