| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Note that there is a typing error that I haven't fixed in login_required
that needs to be solved sometime.
References: https://todo.sr.ht/~runxiyu/fbfp/6
|
| |
|
|
|
|
|
|
|
| |
SQLAlchemy sessions are way too hard to handle with this insane modules
layout. This commit makes everything use Flask-SQLAlchemy.
This commit also creates a simple index.html and adds some CSS.
References: https://todo.sr.ht/~runxiyu/fbfp/2
|
| |
|
|
|
|
|
|
|
| |
I think using SQLAlchemy will be a bit more convenient than using
plain mariadb/sqlite3 bindings, and apparently I figured out how to get
mypy happy with SQLAlchemy 2.0.
I don't really want to use Flask-SQLAlchemy as I don't want that much
vendor lock-in.
|
|
|
I haven't thought of how to structure deployments yet. As I'm planning
to import this under a sub-path in an existing site, it makes the most
sense to use a blueprint. But I also want this to be able to run as a
standalone app.
Part of the issue is that I need to pass in a login_required decorator
from outside. See the referenced ticket.
References: https://todo.sr.ht/~runxiyu/fbfp/1
|
