Private
Public Access
Add configurable article retention (C7)
Articles and full HTML bodies accumulated forever, growing the database, search index, and backups without bound. Site settings gets a "Retention days" field (0, the default, keeps everything); a nightly beat task deletes articles fetched longer ago than that in bounded chunks, always keeping anything a user starred or saved for later. Read state and tags cascade with the article and the FTS triggers drop search entries. The dashboard shows the article count and oldest article's age, and docs/install.md covers retention, the readiness check, and SQLite's WAL tuning. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
e5f1277014
commit
37e658c49a
8 files changed
+166
-6
No files matched your search
+20
-2
@@ -313,8 +313,26 @@ surfaces any feeds that are failing to fetch, which is the fastest way to catch
|
||||
misconfigured feed or an outage at the source.
|
||||
|
||||
`/health/` is an unauthenticated liveness check (DB connectivity only) —
|
||||
`scripts/upgrade.sh` uses it to confirm a deploy actually came back up, and
|
||||
it's a reasonable target for an external uptime monitor too.
|
||||
`scripts/upgrade.sh` uses it to confirm a deploy actually came back up.
|
||||
Point an external uptime monitor at `/health/ready/` instead: it also checks
|
||||
Redis and that the background poller has ticked in the last five minutes
|
||||
(proving Celery beat is scheduling *and* a worker is consuming), and returns
|
||||
503 with a per-check breakdown when any of them fails — so "the site loads
|
||||
but nothing is being fetched" actually alerts.
|
||||
|
||||
**Retention.** By default every fetched article is kept forever. In the Django
|
||||
admin, "Site settings" has a *Retention days* field: set it to delete articles
|
||||
fetched longer ago than that, nightly (03:30 UTC, via Celery beat). Articles
|
||||
anyone has starred or saved for later are always kept; read state and tags for
|
||||
deleted articles go with them. The dashboard shows the article count and the
|
||||
age of the oldest one, so you can see what retention is doing.
|
||||
|
||||
**SQLite.** SQLite installs run in WAL mode with a 20-second busy timeout (set
|
||||
automatically in `config/settings/base.py`) so gunicorn, the Celery worker, and
|
||||
the full-text-search triggers can share the file without "database is locked"
|
||||
errors. That's plenty for a personal or small-team instance; for many users or
|
||||
a very large archive, use PostgreSQL (its search uses a stored, GIN-indexed
|
||||
vector kept current by a trigger, added by migration automatically).
|
||||
|
||||
## Backups
|
||||
|
||||
|
||||
Reference in new issue
Block a user