feat: scaffold newsfeed — user-controlled news feed
Some checks failed
deploy / build (push) Failing after 7s
deploy / deploy-api (push) Has been skipped
deploy / deploy-web (push) Has been skipped

A self-hosted feed where the user owns the ranking: per-source and signed
per-interest weights, decayed by recency, via a transparent deterministic
scorer. Content is sourced algorithmically (worker RSS/Atom polling) and
agentically (per-user API tokens POSTing candidates to the ingest endpoint).
Single-user today, multi-user by construction (every row keyed on user_id).

Rust cargo workspace + Vite/React/SWC/TS SPA:
- newsfeed-entities: DTOs (ts-rs bindings -> web/src/api/bindings)
- newsfeed-core: ranking, auth primitives, ingest, data-access ports
- newsfeed-data: SQLite adapters (sqlx, runtime queries)
- newsfeed-api: axum REST/JSON daemon
- newsfeed-worker: RSS polling + rescoring loop
- web: responsive, mobile-first SPA (React Query, generated types)

Deploy (Gitea Actions, build static musl + SPA, rsync as gitea_ci):
api+worker -> slartibartfast, SPA -> oolon (nginx serves + proxies /v1).

Deliberate deviations from house conventions (documented in CLAUDE.md/readme):
- SQLite instead of Postgres; api+worker co-locate sharing one DB file.
- Runtime sqlx queries instead of query! macros (SQLite dynamic typing;
  keeps CI database-free).

Verified end-to-end: auth, token ingest, interest-weighted ranking, signals,
pagination (curl + browser); cargo fmt/clippy -D/test and pnpm build/lint pass.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016fKZzDpvjiJ9eYbPGgJvUP
This commit is contained in:
2026-07-08 11:36:57 +03:00
commit 5ce52fff4d
104 changed files with 10963 additions and 0 deletions

View File

@@ -0,0 +1,53 @@
# Mesh-only vhost for newsfeed, fronted by the oolon edge proxy (kosherinata site).
# Cert: internal `lair` CA, minted by infra-setup.sh and renewed by step@newsfeed.timer
# (see architecture internal-tls.md). Serves the static SPA and reverse-proxies the API
# to the newsfeed-api daemon on slartibartfast over the WireGuard mesh.
#
# Enable with a relative symlink into sites-enabled (reverse-proxies.md §4):
# ln -sf ../sites-available/newsfeed.internal.conf /etc/nginx/sites-enabled/
upstream newsfeed_api {
server slartibartfast.kosherinata.internal:8081;
keepalive 16;
}
server {
listen 443 ssl;
listen [::]:443 ssl;
http2 on;
server_name newsfeed.internal;
ssl_certificate /etc/nginx/tls/cert/newsfeed.internal.pem;
ssl_certificate_key /etc/nginx/tls/key/newsfeed.internal.pem;
ssl_protocols TLSv1.3;
ssl_trusted_certificate /etc/pki/ca-trust/source/anchors/root-internal.pem;
root /var/www/newsfeed;
index index.html;
# API + health probe → newsfeed-api on slartibartfast.
location /v1/ {
proxy_pass http://newsfeed_api;
proxy_http_version 1.1;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
# For future WebSocket streaming endpoints, add the standard Upgrade/Connection
# map here (define `$connection_upgrade` once in http context).
}
location = /health {
proxy_pass http://newsfeed_api;
}
# Static SPA with client-side routing fallback.
location / {
try_files $uri $uri/ /index.html;
}
# Long-cache the fingerprinted asset bundle.
location /assets/ {
expires 1y;
add_header Cache-Control "public, immutable";
try_files $uri =404;
}
}