Web deploy & Google Sign-In

Official reference · same Expo codebase as the Android app · Source: docs/WEB_DEPLOY.md

Host the Expo web export on Netlify. Point esaheb.com and esaheb.in from Spaceship without moving nameservers or touching email DNS.

Local

cd AllInOneServiceFrontend
npm run web
npm run export:web

Netlify

1. Import AllInOneServiceFrontend (or upload dist).
2. Build: npm run export:web · Publish: dist (see netlify.toml).
3. Env: EXPO_PUBLIC_BASE_URL, EXPO_PUBLIC_GOOGLE_WEB_CLIENT_ID.

Spaceship DNS (both .com and .in)

Keep Spaceship nameservers. Only website records:

Type	Host	Value
A	@	75.2.60.5
CNAME	www	your-site.netlify.app

Do not change MX / TXT / SPF / DKIM.

In Netlify Domain management add: esaheb.com, www.esaheb.com, esaheb.in, www.esaheb.in — wait until HTTPS is Secured for each.

Google Cloud Console (Web client only)

If you open the site on .com or .in, that origin must be listed.

Authorized JavaScript origins

• https://esaheb.com
• https://www.esaheb.com
• https://esaheb.in
• https://www.esaheb.in
• https://allinone-service.netlify.app (optional)
• http://localhost:8081 (local)

Authorized redirect URIs

• https://esaheb.com/oauth-callback.html
• https://www.esaheb.com/oauth-callback.html
• https://esaheb.in/oauth-callback.html
• https://www.esaheb.in/oauth-callback.html
• https://allinone-service.netlify.app/oauth-callback.html
• http://localhost:8081/oauth-callback.html

Do not change the Android OAuth client, package name, or SHA fingerprints.

After Console changes, redeploy Netlify so /oauth-callback.html exists (404 = old deploy).

Android

No Android rebuild required for web hosting. Native Google Sign-In path is unchanged.