Operations
Admin and security
Racinage separates family-user permissions from platform administration. Keep permissions narrow and review public sharing settings before exposing family data.
Family user permissions
Family managers should grant only the permissions a user needs. Tree editing, public sharing, person updates, finance records, and document access should be treated as separate responsibilities.
- Give editing permissions to trusted family maintainers.
- Give view-only access to users who only need to browse records.
- Review user access after major family events or role changes.
Super-admin area
The super-admin area is served separately from admin7839/. It is intended for platform operations such as managing family accounts, system settings, maintenance mode, and support details.
Private data
Family data can include living people, children, phone numbers, locations, financial records, documents, and private history. Treat public share links and exported files as sensitive.
Deployment safety
Production deployment is handled by the repository workflow. Do not commit real secrets or private uploads. The workflow excludes config.php, database dumps, private user media, and other runtime data.
git status
git add docs
git commit -m "Add documentation site"
git push origin mainDatabase changes
When a schema change is needed, apply it intentionally and record the SQL. Performance indexes for large trees should exist on the relationship tables so tree reads do not scan unnecessary rows.