ksmithandClaude Sonnet 5.5 aacb41d1d3 Purge the PWA page cache on every login/logout/expiry transition (R2-S3, #35)
The service worker cached authenticated pages in one origin-wide cache
and only purged it when the logout request itself passed through it —
not on session expiry, externally cleared cookies, or an account
switch, so a shared device could show the previous session's pages
offline.

Every HTML response now carries X-Evection-Auth: an opaque HMAC of the
user (or "anon"), via a small middleware. The service worker remembers
the marker its cached pages belong to and, whenever a navigation brings
a different one, deletes the pages cache before storing anything; "anon"
responses (the login page) are never cached. So the cache always holds
exactly one session's pages, and any transition the worker can observe
online clears it. (What no design can detect is a session ending while
the device stays offline.)

Verified in a real browser: pages cached after login; expiring the
session server-side (no logout request) and loading a page left the
cache deleted and the marker "anon"; logging in as a second user
afterward cached only that user's pages, none of the first user's.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-01 12:05:45 -07:00

Evection

A self-hosted RSS/Atom feed reader, in the spirit of FreshRSS, built in Python (Django) instead of PHP. Installable as a PWA on your phone, with offline reading for anything you've already loaded.

Features

  • Multi-user, with per-user folders, read/starred/saved-for-later state, and tags
  • Background feed polling via Celery, with conditional GET and backoff on errors
  • Full-text search over your articles (SQLite FTS5 or PostgreSQL, your choice)
  • A filter/rules engine to auto-tag, star, hide, or mark feeds' articles read
  • OPML import/export
  • Installable as a PWA (Add to Home Screen) with an offline fallback page
  • An admin dashboard surfacing feeds that are failing to fetch

Deploying your own instance

See docs/install.md for a production install: pip + gunicorn

  • systemd + nginx, with both SQLite and PostgreSQL covered.

Development setup

python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
cp .env.example .env
python manage.py migrate
python manage.py runserver

Visit http://localhost:8000/ — you'll land on the first-run setup wizard to create the instance's admin account.

Updating pinned dependencies

requirements.txt/requirements-dev.txt are hash-pinned lock files generated from pyproject.toml — production installs (scripts/install.sh, scripts/upgrade.sh) install from requirements.txt with --require-hashes rather than re-resolving version ranges at install time. After changing a dependency in pyproject.toml, regenerate both and commit them alongside:

pip-compile --generate-hashes --allow-unsafe --output-file=requirements.txt pyproject.toml
pip-compile --generate-hashes --allow-unsafe --extra=dev --output-file=requirements-dev.txt pyproject.toml

Tests

pytest
ruff check .
black --check .

Testing against PostgreSQL

The suite runs on SQLite by default; the Postgres-only tests (search backend) are skipped there. To run everything against a real Postgres:

docker run -d --name evection-pg-test -e POSTGRES_PASSWORD=testpw -e POSTGRES_DB=evection \
    -p 127.0.0.1:55432:5432 postgres:16
DATABASE_URL=postgres://postgres:testpw@127.0.0.1:55432/evection pytest
docker rm -f evection-pg-test

License

GNU AGPL-3.0-or-later — if you run a modified version of Evection as a network service, you must make your modified source available to its users.

S
Description
Web RSS Feed Reader
Readme AGPL-3.0
1.4 MiB
0 Stars 0 Watchers 0 Forks
Languages
Python 82.7%
HTML 5.5%
Shell 4.4%
JavaScript 4.2%
CSS 3.2%