History

zai-bot 621bbc662c v7.15.3 — self-healing sandbox boot: tracked .env.ove + db seed + secrets/ Operator-authorized for the strictly private self-hosted Forgejo repo: the env template (.env.ove), a baseline database snapshot (db/custom.db.seed) and secrets/ now ride with the repo so sandbox reprovisions can never wipe them. dev.sh self-heals at the very top (before bun install): .env is restored from .env.ove whenever it lacks OVE_DIRECTORY_API_KEY, and db/custom.db from the seed whenever it is missing — verified end-to-end against a faithful reset simulation (both [SELF-HEAL] restores fire, 106-preset library serves, directory proxy authenticated, browser clean). One evidence-driven deviation from the requested values: DATABASE_URL is file:../db/custom.db, not file:./db/custom.db — Prisma resolves relative SQLite paths against prisma/schema.prisma's directory, so the ./ form provably breaks both the CLI (would create a fresh empty db at prisma/db/custom.db on every boot) and the runtime (cannot open); the ../ form is the portable equivalent and is documented in .env.ove's header. secrets/ ships with a README documenting the house-cookie file slots (the actual cookie exports are re-added by the operator).	2026-11-06 08:00:46 +00:00
..
README.md	v7.15.3 — self-healing sandbox boot: tracked .env.ove + db seed + secrets/	2026-11-06 08:00:46 +00:00

zai-bot 621bbc662c v7.15.3 — self-healing sandbox boot: tracked .env.ove + db seed + secrets/

Operator-authorized for the strictly private self-hosted Forgejo repo:
the env template (.env.ove), a baseline database snapshot
(db/custom.db.seed) and secrets/ now ride with the repo so sandbox
reprovisions can never wipe them. dev.sh self-heals at the very top
(before bun install): .env is restored from .env.ove whenever it lacks
OVE_DIRECTORY_API_KEY, and db/custom.db from the seed whenever it is
missing — verified end-to-end against a faithful reset simulation
(both [SELF-HEAL] restores fire, 106-preset library serves, directory
proxy authenticated, browser clean).

One evidence-driven deviation from the requested values: DATABASE_URL
is file:../db/custom.db, not file:./db/custom.db — Prisma resolves
relative SQLite paths against prisma/schema.prisma's directory, so the
./ form provably breaks both the CLI (would create a fresh empty db at
prisma/db/custom.db on every boot) and the runtime (cannot open); the
../ form is the portable equivalent and is documented in .env.ove's
header. secrets/ ships with a README documenting the house-cookie file
slots (the actual cookie exports are re-added by the operator).

2026-11-06 08:00:46 +00:00

README.md

v7.15.3 — self-healing sandbox boot: tracked .env.ove + db seed + secrets/

2026-11-06 08:00:46 +00:00

README.md

secrets/ — house-account cookies (TRACKED by operator authorization)

This directory is committed to the private, self-hosted Forgejo repository (gitzcreations/openvisengine) by explicit operator authorization, so a sandbox reprovision can never wipe the house accounts. Do not publish this repository anywhere public while these files exist.

What belongs here

Netscape cookies.txt exports of the operator's "house" music-service accounts, one file per service. Stream-a-Link attaches them server-side as the shared fallback login when a visitor has no saved login of their own:

house-youtube-cookies.txt — YouTube / YouTube Music
house-soundcloud-cookies.txt — SoundCloud
house-spotify-cookies.txt — Spotify
house-apple-cookies.txt — Apple Music

Loaded by src/lib/server/house-cookies.ts: read server-side only, the status endpoint exposes booleans (never cookie contents), and a visitor's own saved login always takes precedence over the house account.

After a sandbox reset

Nothing to do — git checkout restores this directory and the app picks the files up on boot. (The 2026-11-06 reprovision lost the original files before this directory was tracked; the operator re-exports them once and they are safe from then on.)