aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* Rename view->work and deny access to private onesRunxi Yu2024-05-304-15/+24
|
* Click into titles to reach the view pageRunxi Yu2024-05-302-2/+3
|
* Top-align index.html's flex columnsRunxi Yu2024-05-301-4/+5
|
* Disclaimer and versionRunxi Yu2024-05-303-0/+62
|
* Display text submissionsRunxi Yu2024-05-303-6/+24
|
* List all works on user/self pageRunxi Yu2024-05-301-1/+1
|
* List public works in user pagesRunxi Yu2024-05-301-5/+20
|
* "/view/<wid>" allows viewing a workRunxi Yu2024-05-308-33/+197
|
* Allow new submissions (supports uploads)Runxi Yu2024-05-3010-17/+413
| | | | | | | 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
* Basic table template for "my work" and "others' work"Runxi Yu2024-05-293-13/+62
|
* index.html: Add flexboxRunxi Yu2024-05-292-31/+44
|
* dev.sh: Use the venv's interpreterRunxi Yu2024-05-291-1/+1
|
* Remove Chinese characters from testing name and reformat codeRunxi Yu2024-05-291-10/+16
|
* Use Flask-SQLAlchemy instead; add basic html/cssRunxi Yu2024-05-297-33/+276
| | | | | | | | | 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
* Add pyproject.toml and initialize SQLAlchemyRunxi Yu2024-05-297-0/+86
| | | | | | | | | 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.
* FormattingRunxi Yu2024-05-291-1/+8
|
* no_login_required context should include oid, name, preferred_usernameRunxi Yu2024-05-291-3/+2
|
* The login_required decorator should give the route a fake auth contextRunxi Yu2024-05-291-4/+15
| | | | | | | | | | | Previously I just used an identity function for login_required. But a real login_required decorator (at least, what is provided by github.com/rayluo/identity) would give the wrapped function a "context" argument which includes data such as the login name and the email address. This is, of course, necessary, so I made a new function (no_login_required) that just passes a fake login context. References: https://todo.sr.ht/~runxiyu/fbfp/1
* Move templates into fbfp/Runxi Yu2024-05-291-0/+0
|
* Reformat fileRunxi Yu2024-05-291-1/+3
|
* Use a Python package instead of a module fileRunxi Yu2024-05-291-0/+0
|
* Add debugging scriptRunxi Yu2024-05-291-0/+5
|
* Make a debug-only app factory and use it in __main__Runxi Yu2024-05-291-2/+5
|
* Register all routes in make_bp(login_required)Runxi Yu2024-05-282-24/+20
| | | | | | | | I don't think this is the best-looking way to do it, and it does mean that my indentation is a mess, but it's the sanest way that I can imagine. References: https://todo.sr.ht/~runxiyu/fbfp/1
* Add a dummy login_required function for developmentRunxi Yu2024-05-284-0/+64
| | | | | | | | | | | | 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
* README.md: Initial questions, potential goals, etc.Runxi Yu2024-05-272-0/+677
generated by cgit v1.2.3 (git 2.39.1) at 2024-10-05 05:31:06 +0000