Configuring OAuth & Third-Party Integrations

When you run create-stackr, the CLI auto-fills every secret it can generate itself — the database and Redis passwords, and the 64-character hex BETTER_AUTH_SECRET. Those are ready to use the moment init finishes.

Third-party secrets are different: stackr can't invent a Google client ID or a RevenueCat API key for you. Those land in your .env and app.json files as placeholders (for example YOUR_GOOGLE_WEB_CLIENT_ID) that you replace with real values from each provider's dashboard.

Find what's still unconfigured

Rather than grepping for placeholder strings by hand, run the config command. It reports every integration that is enabled for your monorepo but still holding a placeholder:

npx stackr config

To fill the values in without hand-editing files, run it interactively — it prompts for each unconfigured field and writes the value back to the right .env or app.json:

npx stackr config --interactive

The rest of this page walks through where each integration's values live and how to obtain them from the provider.

Google OAuth

The web client ID and secret live in the auth service's backend/.env. The iOS and Android client IDs are configured separately in mobile/app.json under extra.googleOAuth.

Dashboard: console.cloud.google.com

1. Open the Google Cloud Console.
2. Create OAuth 2.0 credentials for Web, iOS, and Android.
3. Copy the Web client ID into GOOGLE_WEB_CLIENT_ID and the client secret into GOOGLE_CLIENT_SECRET in the backend .env.
4. iOS and Android client IDs are configured in mobile/app.json under extra.googleOAuth.

GOOGLE_WEB_CLIENT_ID=1234567890-abcdefg.apps.googleusercontent.com
GOOGLE_CLIENT_SECRET=GOCSPX-your-real-secret

Apple Sign In

Apple's values all live in the auth service's backend/.env.

Dashboard: developer.apple.com

1. Open the Apple Developer portal.
2. Create a Service ID for the web OAuth flow and set APPLE_SERVICE_ID.
3. Set APPLE_BUNDLE_ID to your app bundle id for native iOS ID token verification.
4. Generate a client secret JWT signed with your Apple private key and set APPLE_CLIENT_SECRET.

GitHub OAuth

Both GitHub values live in the auth service's backend/.env.

Dashboard: github.com/settings/developers

1. Open GitHub Developer settings and register a new OAuth app.
2. Copy the client ID into GITHUB_CLIENT_ID in the backend .env.
3. Generate a client secret and copy it into GITHUB_CLIENT_SECRET.

Email (SMTP)

Email verification and password reset both send mail through SMTP. The credentials live in the auth service's backend/.env, and the template defaults to Gmail (smtp.gmail.com:587).

Dashboard: Gmail app passwords

1. Choose an SMTP provider (the template defaults to Gmail at smtp.gmail.com:587).
2. For Gmail, create an app password and set it as SMTP_PASS.
3. Set SMTP_USER to the sending account and EMAIL_FROM to the from address.

SMTP_USER=notifications@yourcompany.com
SMTP_PASS=your-app-password
EMAIL_FROM=notifications@yourcompany.com

Mobile SDKs

The mobile integrations store their keys in mobile/app.json under extra.* rather than in .env, because Expo embeds them into the native build via expo-constants. After changing any of these, rebuild the app so the new values are picked up.

RevenueCat

Dashboard: app.revenuecat.com

1. Open the RevenueCat dashboard and create a project.
2. Copy the iOS public API key into extra.revenueCat.iosKey in mobile/app.json.
3. Copy the Android public API key into extra.revenueCat.androidKey in mobile/app.json.
4. Rebuild the app so the keys are embedded via expo-constants.

{
"expo": {
  "extra": {
    "revenueCat": {
      "iosKey": "appl_yourRealIosKey",
      "androidKey": "goog_yourRealAndroidKey"
    }
  }
}
}

Adjust

Dashboard: dash.adjust.com

1. Open the Adjust dashboard and create an app.
2. Copy the app token into extra.adjust.appToken in mobile/app.json.
3. Set extra.adjust.environment to "sandbox" while testing and "production" for release.
4. Rebuild the app so the values are embedded via expo-constants.