Onboarding checklist
Work through this list in order. Most items need someone else to act, so request them all on day one and install software (Workstation setup) while you wait. Names of the people to ask are on the who to ask page.
1. Accounts and access
| Item | Needed for | Ask | Notes |
|---|---|---|---|
GitHub membership of Every-Man-A-Warrior | All code | Project owner | Work from develop; main deploys |
Google Workspace account (@everymanawarrior.com) | Cloudflare Access (dev website, admin CRM, these docs), Google Meet features | Project owner | Only Workspace accounts pass Cloudflare Access |
| Tailscale invite to the tailnet | Dev database, SSH to any VM | Troy or Matt | Without it the dev DB and VMs are unreachable |
| SSH user with your public key on the dev Django VM (and the prod DockerApp VM if you will deploy) | Tunnel hand-over, server-side docker compose | Troy or Matt | Key-only; there is no password auth |
.env for the backend | Running the backend | Project owner, via the password manager | Never commit, paste or email it |
Expo / EAS access to the EMAW project | Mobile builds | Project owner | Also an Apple Developer and Google Play Console role if you will submit |
| Stripe dashboard access (test mode) | Store, events, donations work | Project owner | Test-mode keys only in dev |
Azure portal access to EMAW-Development and EMAW-APP-RG | Infrastructure changes, logs, blob | Matt | Read-only is enough to start |
| Cloudflare account access | DNS, Pages, Workers, R2, tunnels, Access | Matt | Needed to create Pages projects or Access policies |
| Portainer IP whitelist | Production backend deploys | Matt Birne | Your public IP must be allow-listed |
| CRM Staff Django group (or capabilities) on your dev app account | Signing in to the Admin CRM against dev | Any superuser via Django admin | Create your account on the dev website first |
2. Read these
- Platform overview and Architecture.
- Access and security. Short, and it is where the rules that bite live.
- Environments overview so the hostnames make sense.
- The repository's own
CLAUDE.md/README.mdfor the app you are starting on.
3. First tasks, by app
- Backend: follow Backend local development up to a running stack, then run the test suite once.
- Website: Website local development, then place a test order on your local build against the dev backend with a Stripe test card.
- Admin CRM: Admin CRM local development, sign in with your dev account and open the Contacts list.
- Web app: Web app local development, then test the hand-off from a local website build.
- Mobile: Mobile workstation setup and get a development build running on an Android emulator.
4. When you are set up
- Post in the team channel which laptop will be running the dev tunnel so nobody takes it over mid-session.
- Add yourself to the who to ask page if you own something.