FOR ANDREW
Connect the live clubhouse.
The site uses your Supabase project for standalone accounts, protected league records, and private attachments. The publishable key is public application configuration; no secret key is embedded.
1. Install the database
Preparing the complete SQL file.
On iPhone: tap Copy setup SQL, open the SQL Editor below, touch and hold inside the blank editor, then tap Paste and Run.
- Download the setup SQL.
- Open your project’s SQL Editor.
- Paste the complete SQL file and select Run. It creates the protected schema, competition rules, and private file bucket. Re-running it preserves league data.
2. Configure account links and email delivery
In Supabase Authentication → URL Configuration, set the Site URL to:
https://app.matchsteward.org
Add the same address with a trailing slash to the allowed Redirect URLs:
https://app.matchsteward.org/
Keep Confirm Email enabled. Configure a production SMTP provider before inviting 30 players; Supabase’s default mail service restricts recipients and sending volume. League email and text features are excluded, but account verification and password recovery still use email.
3. Create and verify your owner account
Use the owner email you supplied, create a password, verify the email, and sign in. The designated verified account receives the initial course-manager role. Other users do not choose their own staff permissions.
Open Matchsteward →4. Rehearse before inviting everyone
- Check and, if needed, edit the three nines in Course settings. Confirm the par, difficulty ranks, and tee reference information.
- Configure the initial stroke-play competition. Select each round’s first and second nine, then open scoring.
- Use Invitations to copy its code. Have a second real account request entry; approve entry and Course Handicap.
- Post scores from two devices and verify the gross/net leaderboard. Test a conflicting edit and a staff correction.
- Disconnect one device, save a score, reconnect, and verify synchronization.
- Confirm the completed card and finalize the round. Compare the totals with a backup card.
A published interface and passing local tests do not establish that the hosted account, email, and database flows are verified. Keep backup scorecards during the pilot. This test is independent and is not an official Crosswinds Golf Club service.