Deploy (CPU/CUDA images, Cloudflare Tunnel, backups) and a new README with docs/

[botta0oss]

Docker images

• Dockerfile (default): installs PyTorch from the CPU-only index, so servers no longer download the CUDA build (several GB). The build fails if a CUDA torch slips in.
• Dockerfile.cuda: keeps the CUDA build for a local NVIDIA GPU. docker-compose.gpu.yml switches the api service to it and reserves the host's GPUs.
• Distinct image tags (news-aggregator-api:cpu / :cuda). The startup log says which device the embedding model uses.

Deploy on a VPS with Cloudflare Tunnel

• Compose: database password from POSTGRES_PASSWORD in .env; app port bound to 127.0.0.1 (API_BIND); restart: unless-stopped on every service.
• Optional profiles:
  • tunnel: cloudflared with CLOUDFLARE_TUNNEL_TOKEN, HTTPS with no open ports.
  • backup: daily pg_dump in ./backups, keeping BACKUP_KEEP_DAYS days.
• CLIENT_IP_HEADER=CF-Connecting-IP: behind the tunnel every request comes from cloudflared, so without it the login limits would treat everyone as one IP.
• scripts/update.sh: pulls, rebuilds and restarts.
• .env.example: DEFAULT_FEE_BPS and MARKET_NEWS_WINDOW_HOURS aligned with the current defaults. A copied .env was overriding them with the old values.

Local and home-network use

• docs/deploy.md: running locally needs no tunnel, because the optional services are profiles. To open the dashboard from other devices at home, set API_BIND=0.0.0.0 and SESSION_COOKIE_SECURE=false, with a warning about plain HTTP.
• docs/configurazione.md: lists the Docker compose variables.
• Login: when the password is right but the browser refuses the session cookie (a Secure cookie over plain HTTP from a network address), the form now says so and names the setting. Before, it silently showed the login again. Checked in a browser in three cases:
  • via a network address with auto: the message appears;
  • via localhost with auto: sign-in works;
  • via a network address with false: sign-in works.

README and documentation

• README as a landing page:
  • centered header with badges and quick links;
  • hero screenshot, features grid, screenshot gallery (light and dark via <picture>);
  • how it works (diagram and five steps);
  • quick start, hosting costs, essential configuration;
  • documentation index, tech stack, known limits.
• docs/: the previous sections split by topic, with an index. Internal links were rewritten across pages and checked.
• Out-of-date content fixed along the way:
  • known limits: multi-outcome markets are supported, and fees no longer come from takerBaseFee;
  • dashboard table: added Cosa fare, Portafoglio, Uso e costi, and intervals and CLV in Calibrazione;
  • pipeline table, project tree, test list, and the local-install note about migrations.
• docs/images: screenshots of the demo data, about 1.1 MB in total; docs is excluded from the Docker build context.

Verification

• Tests: 184 pass.
• Compose: docker compose config resolves all combinations.
• Backup: the loop was run against a local Postgres; the dump was restored and the row counts match.
• Docs:
  • no content lost in the split: every line of the old README is present in the new pages, except the lines intentionally rewritten;
  • all relative links and images resolve.
• Not run here: there is no Docker daemon, and download.pytorch.org and shields.io are blocked by this environment's proxy. The images, the live tunnel and the badges were not exercised.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JLWZrfy12imc6dQRsEtFjj