Jason C. McDonald

Documentation is crucial. No project is production-grade without it. I do a lot of "for free" open source work myself, so I'm not numb to that. I've also defended maintainers...

Six years in, any progress on this? Even a `README` would be helpful at this point. I *might* be able to help with packaging on Debian if we've got that...

``` 86421 [2021-02-16 14:31:20.295] [foreground] [info] -- No messages found. Sleeping 1 to wait for sent folder to settle... 86421 [2021-02-16 14:31:21.401] [foreground] [info] -- No messages found. Sleeping 1...

Based on the logs, it was looking for UID `1355`. However, according to later logs, UID `1356` was the correct UID for the message? ``` 86421 [2021-02-16 14:50:30.745] [background] [info]...

Use https://github.com/escaped/idle_time, which also depends on https://pypi.org/project/jeepney/

When I used the current settings section and default static file route, I got the error stated. (I have not been having fun.)

I'm getting much the same error on `makemigrations` and `migrate`, along with some further warnings about accessing during initialization (fresh database). ``` /opt/horilla/venv/lib/python3.10/site-packages/django/db/backends/utils.py:98: RuntimeWarning: Accessing the database during app initialization...

That appears to fix both issues, so perhaps this is related to Django 5 altogether. (Mind you, I'm getting a 500 when serving via Apache2, but I suspect that's altogether...

Correction, it does _not_ fully fix it. I have this error still on `makemigrations`: ``` elation "pms_employeeobjective" does not exist LINE 1: ...rcentage", "pms_employeeobjective"."archive" FROM "pms_emplo... ^ relation "pms_employeekeyresult" does...

Fresh database.