firebase-deploylisted

Deploy the ontology-atlas static site to Firebase Hosting from this repo. Use when the user asks to deploy, redeploy, publish the site, update Firebase Hosting, or verify the live web.app URL. The workflow must read `.env.prod`, build the static export, deploy only Hosting, and verify the live URL. Never commit `.env.prod` or introduce Firebase backend services.
wlsdks/ontology-atlas · ★ 1 · AI & Automation · score 67

Install: claude install-skill wlsdks/ontology-atlas

# /firebase-deploy — static Firebase Hosting deploy This project deploys as a pure static export. Firebase is only the file host: no Functions, Firestore, Storage, Auth, emulators, or server runtime. ## Required local file Read `.env.prod` at the repo root before deploying. It is gitignored and should contain deployment identifiers only: ```bash FIREBASE_PROJECT_ID=ontology-atlas FIREBASE_HOSTING_URL=https://ontology-atlas.web.app FIREBASE_HOSTING_ALT_URL=https://ontology-atlas.firebaseapp.com ``` Do not print or commit tokens, service account JSON, refresh tokens, or npm publish credentials. If `.env.prod` is missing, stop and ask the user to create it or provide the Firebase project id. Use `.env.prod.example` as the non-secret template. For GitHub-hosted deploys, `.github/workflows/deploy-hosting.yml` is the website-only path for manual dispatch or human-created Release events. The macOS tag release workflow does not require Firebase secrets and does not deploy Hosting; the installed app remains local-only. The Hosting path expects these repository settings: - secret: `FIREBASE_SERVICE_ACCOUNT_JSON` - variables: `FIREBASE_PROJECT_ID`, `FIREBASE_HOSTING_URL`, `FIREBASE_HOSTING_ALT_URL` (defaults match `.env.prod.example`) The workflow writes a temporary `.env.prod`, sets `NEXT_PUBLIC_OATLAS_FIRST_RELEASE_PENDING=0`, runs `pnpm firebase:deploy-check`, deploy only Hosting with `firebase-tools@15.17.0`, and verify the live download route. Release-published runs autom