1.9 KiB
Public repository and deployment privacy
Runtime keys, passwords, sessions, private photos, databases and local .env files
must remain outside Git. Examples use documentation-only addresses and identities.
Personal deployment reports and screenshots are excluded from public history.
The Gitea NAS Docker runner accepts trusted repository events only. GitHub mirrors use the separate community workflow on GitHub-hosted disposable runners, with read-only repository permissions and no deployment configuration. External fork PRs are not executed on this runner; maintainers must review them before copying changes to a trusted branch. All lint, type, test, audit and isolated Docker checks remain.
Public CI verifies source only. Runtime configuration belongs in private environment files or the deployment system's secret store. Never print complete Docker inspect environment or secret values.
Before publishing, scan the current source and distribution files for secrets and private receipts. Keep Git history and existing remote releases. If a real historic secret is found, revoke it and handle history remediation as a separate operation.
Private deployment inputs
Do not publish host addresses, workstation paths, disk UUIDs, photo-library counts, or deployment receipts. Do not include deployment receipts or recovery bundles in published archives. Local obsolete artifacts may be removed after verification; active runtime configuration, databases and images must be preserved.
server-release.py reads FRAME_FLOW_ROOT (default /srv/frameflow), requires
FRAME_FLOW_MOUNT_UUID and FRAME_FLOW_ORIGIN, and retains the mount-identity
check before release actions. Supply verified values privately to the sudo process;
existing installations must set their existing root explicitly. Do not use the
generic default to migrate a deployment. The script still requires the existing
mount guard and does not change host mounts, services, or storage automatically.