agentleFS
firebasefirebase/agent-skills/skills/firebase-app-hosting-basics/SKILL.md

firebase-app-hosting-basics

Skill506 starsChanged 5 months agoApache-2.0View on GitHub

Deploys and manages full-stack web applications (Next.js, Angular) with Server-Side Rendering (SSR) using Firebase App Hosting. Use when deploying Next.js/Angular apps, configuring apphosting.yaml or firebase.json apphosting blocks, managing secrets, setting up GitHub CI/CD, or configuring Blaze billing requirements. Don't use for classic static web hosting, Auth, Firestore, Crashlytics, or Xcode.

  • Reads credentials
  • Commits and pushes

4 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create or edit apphosting.yaml- see Configuration for more information on how to do so.

    line 62
  2. Very specific:

    Create the backend if it does not exist (apphosting:backends:list.

    line 66
  3. Very specific:

    Run npx -y firebase-tools@latest deploy when you are ready to deploy.

    line 81

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

App Hosting Basics

Description

This skill enables the agent to deploy and manage modern, full-stack web applications (Next.js, Angular, etc.) using Firebase App Hosting.

Important: In order to use App Hosting, your Firebase project must be on the Blaze pricing plan. Direct the user to https://console.firebase.google.com/project/_/overview?purchaseBillingPlan=metered to upgrade their plan.

Hosting vs App Hosting

Choose Firebase Hosting if:

  • You are deploying a static site (HTML/CSS/JS).
  • You are deploying a simple SPA (React, Vue, etc. without SSR).
  • You want full control over the build and deploy process via CLI.

Choose Firebase App Hosting if:

  • You are using a supported full-stack framework like Next.js or Angular.
  • You need Server-Side Rendering (SSR) or ISR.
  • You want an automated "git push to deploy" workflow with zero configuration.

Deploying to App Hosting

Deploy from Source

This is the recommended flow for most users.

  1. Configure firebase.json with an apphosting block.

    {
      "apphosting": {
        "backendId": "my-app-id",
        "rootDir": "/",
        "ignore": [
          "node_modules",
          ".git",
          ".next",
          ".vercel",
          "firebase-debug.log",
          "firebase-debug.*.log",
          "functions"
        ]
      }
    }
  2. Create or edit apphosting.yaml- see Configuration for more information on how to do so.
  3. Create the backend if it does not exist (apphosting:backends:list; switch --primary-region, e.g. us-east4, if a region hits its 10-backend quota):

    npx -y firebase-tools@latest apphosting:backends:create --backend my-app-id --primary-region us-central1 --root-dir /
  4. For sensitive keys/secrets (e.g., from .env*), set and grant access after creating the backend and reference via secret: (never value:):

    printf '%s' '<value>' | npx -y firebase-tools@latest apphosting:secrets:set <secret-name> --data-file - --force
    npx -y firebase-tools@latest apphosting:secrets:grantaccess <secret-name> --backend my-app-id
  5. Run npx -y firebase-tools@latest deploy when you are ready to deploy.

Automated deployment via GitHub (CI/CD)

Alternatively, set up a backend connected to a GitHub repository for automated "git push" deployments. For GitHub-connected backends, trigger rollouts with npx -y firebase-tools@latest apphosting:rollouts:create <backend-id> --git-branch <branch> (do not use rollouts:create when deploying from local source with deploy).

For other backend or secret flags (backends:get, backends:delete, etc.), run npx -y firebase-tools@latest <command> --help.

Emulation

See Emulation for more information on how to test your app locally using the Firebase Local Emulator Suite.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.