New feeds are not updated until the update command is run about reader HOT 3 CLOSED

Possible solutions:

1. Worker thread running alongside the app. Who manages/owns it when running under uWSGI? Bad.
2. Task queue (e.g. Celery). Big dependency. Too much to set up.
3. Worker process listening on a socket. Is a service. Additional setup. Too complicated.
4. Polling the database.
   4.1. Worker process (updating only new feeds). Is a service. Might be too resource intensive depending on interval; might not.
   4.2. cron every 1 minute (updating only new feeds). Might need to ensure no more than one process runs at a time (if update takes longer than 1 minute); might not (the backlog of new feeds shouldn't be too big), but we might pull some feeds twice (unlikely). Might be too slow; might be good enough.

from reader.

Implemented 4.2. Let's see how that goes.

from reader.

Seems good enough.

from reader.