antonpaquin / homulili Goto Github PK

Make remote deploy easier

Files are the primary pain point of this iteration of the program. GUI to view / manage would be good

Right now you click the button and hope. It should feel like they're doing something.

Give frontend an RSS view (esp on chapter.index operations)

Do we ignore scanned files by default until they've been approved?
Provide a way to delete a downloaded file?

The FSM of files is rather badly defined right now, make that explicit + good

Backend:
[key] [permissions]

Frontend:
[user] [pass_hash] [salt] [api_key]

Will also probably require the creation of user endpoints

Instead of raw SQL, a model layer is probably nicer

According to https://mail.python.org/pipermail//python-list/2009-January/519146.html (most likely explanation?)
The error is that zips created under some specific set of circumstances will have junk data somewhere that makes python give up trying to parse them.

let the static stuff be static

Probably with a decorator + header
Let's hold off on user-level auth for now -- this one can be the root level auth token

Break only when the stage's total error count goes over the total limit -- if a single input hits the single limit, just drop that input and continue

Probaby leave bots on admin, but authenticated frontend routes should be using the one grabbed from the table

Logs (and comments) needed everywhere

I want to have file errors include tracebacks, and the mess that is dataflow is preventing that