Setup React Ios Remote

Standard questions (answer with the user before changing files)

1. Framework: Expo (recommended for faster iteration) or bare React Native?
2. Repo layout: monorepo root, apps/mobile, or single app folder?
3. Mac mini: hostname/IP, SSH user, full path to the checkout (e.g. ~/src/gratifire).
4. Signing: Apple Developer team, bundle ID, provisioning (manual vs automatic), and where certificates live (Keychain on mini only).
5. Node: version pinned via .nvmrc / fnm / asdf on both dev machine and mini.

SSH development pattern

Document for the team:

# Example — adjust user, host, and path
ssh [email protected]
cd ~/src/gratifire
git pull
# Install JS deps on mini when native or lockfile changes
npm ci   # or pnpm install / yarn install
# iOS native deps (React Native / prebuild)
cd ios && pod install && cd ..
# Build (example)
xcodebuild -scheme Gratifire -configuration Debug -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 16'

Rules for agents:

• Prefer non-interactive flags; use CI-friendly environment variables for signing when possible.
• Never commit secrets, p12 files, or App Store Connect passwords; use Keychain on the mini and CI secret stores.
• If a command must run only on macOS, state explicitly that it runs via SSH on the Mac mini.

Deliverables checklist

• In the game repo (slbailey/gratifire): README or docs/DEV_MAC_MINI.md with SSH host, paths, and copy-paste commands
• Node version file and package manager lockfile committed
• iOS bundle identifier and scheme name recorded
• First successful Simulator build from a clean clone on the mini

Coordination

• ios-build-engineer: owns Xcode, CocoaPods, signing, and Simulator/device runs on the mini.
• react-specialist: owns app structure, React patterns, and JS tooling.
• devops-engineer: optional CI that SSHs or uses a macOS runner to repeat the same steps.