BaileyOS
This repository holds the BaileyOS pages for operation Red Robin: Landing Stone, Signal Ark, and the 81 Canon Bible. The home screen links to each app.
Signal Finder stays a separate tool at signal-beacon-compass.lovable.app. Landing Stone and Signal Finder used to share one app. They are now separate. Landing Stone stays in this repo.
Expected home URL: https://swaggconsultingllc.github.io/BaileyOS-/
Apps
GitHub Pages
Pages is published by the Publish Bailey OS workflow in .github/workflows/pages.yml. It runs on every push to main, and it can be started by hand. The job checks out the repository and uploads the repository root (path: .) as the Pages artifact, then deploys that artifact. .nojekyll is in the root, so Pages serves the files as they are. That includes the home screen, landing-stone/, signal-ark/, and canon/.
Open index.html in a browser for the same home screen locally.
Signal Ark sign-in
Beneficiary records are private. They are stored in Supabase (table ark_beneficiaries) and are only shown after sign-in. Anyone can view the scripture and signal pages without signing in.
To use the beneficiary dashboard, a person needs two things:
- A Supabase account (email + password) in the BaileyOS Supabase project. The project owner adds it in the Supabase dashboard under Authentication → Users → Add user.
- A role in the
user_roles table set to owner or steward, linked to that account's user ID. Without that row, the person can sign in but sees no data.
Then open Signal Ark, go to the Dashboard tab, and sign in with that email and password. The page uses only the public Supabase key. Database rules allow access only for signed-in owners and stewards.
Supabase
The 81 Canon reading log uses the project BaileyOS Signal Finder Compass (rxckxwdvhjszzuqsvxdk). Opening a chapter writes a row to public.canon_reads. The table has row-level security: anyone may insert and read that log, and nothing else. The publishable key is in canon/config.js.
