docs: housekeeping - branch policy, Tailscale sidecar deployment (no host coupling), dedicated import cron plan

This commit is contained in:
AlexanderRozhenko
2026-11-10 18:09:16 -04:00
parent 18bf31f361
commit 670648b17a
3 changed files with 24 additions and 12 deletions

View File

@@ -27,9 +27,15 @@ A private, Tinder-style web app for browsing the motorcycle market: swipe real l
- [`docs/UI-SPEC.md`](docs/UI-SPEC.md) — screens, gestures, Tinder-fidelity goals
- [`docs/PLAN.md`](docs/PLAN.md) — phases, acceptance criteria, status
## Branches
- `main` — stable trunk (docs + verified code); the default branch.
- `dev` — active development; build work lands here first.
- `release` — deployable cuts; the Rotarran stack tracks this branch.
## Deployment (planned)
A small podman compose stack on the Rotarran under `/var/mnt/DATA/podman-stacks/bike-tinder/`, its own systemd user unit (`Delegate=yes`), SQLite database, published to the tailnet only via `tailscale serve` on port 9453. Single user; no auth beyond the tailnet.
A small podman compose stack on the Rotarran under `/var/mnt/DATA/podman-stacks/bike-tinder/`, its own systemd user unit (`Delegate=yes`), SQLite database. The stack ships its own Tailscale node (sidecar container — no host-tailnet coupling) and serves the app privately at `https://biketinder.tailf35a34.ts.net`. Single user; reachable only from Glenn's own devices.
## Crew