38 results found

1. Support Next.js Image Optimizations

   Using Next/Image on Firebase App Hosting makes images load slowly. Are Next's built-in image optimizations working with Firebase App Hosting? When a second container starts, does the new container need to optimize every image again, or do containers share image files somehow? When a container shuts down, are those optimized images lost, or are they stored in persistent file storage?

   15 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  App Hosting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Add a Preview environment for App Hosting deployments.

   As a developer, I want to be able to deploy my Next.js web app hosted using App Hosting to a Preview "channel", similar to firebase hosting:channel:deploy in hosting.
   Thanks.

   26 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  App Hosting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Add npm workspace support for monorepos

   App Hosting already supports nx based monorepos, but it would be great to have basic npm workspace support. I tried to take the plunge and convert my repo to nx tooling but I failed spectacularly 🙂 npm workspaces are super simple to get started with and other than not being able to deploy to App Hosting, they haven't come up short for me in a way that would convince me to try nx again.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  App Hosting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Add auth handlers from Hosting to App Hosting.

   /__/auth/handler

   Identical to hosting but for app hosting.

   Would definitely make things simpler for Next.js apps.

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Streamline the process of adding .env variables to the build configuration

   I like the idea that you can use Cloud Secret Manager to store and encrypt the secrets within the app.

   Coming from using .env files in Next.js and Vercel hosting could this process be made simpler e.g. reading the .env file from your app directly and intelligently placing the key/value pairs in the apphosting.yaml file or the rollout during creation.

   This would be good to keep things simple and straight forward.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. create a UI for managing environment variables and surfacing build error messages in the Firebase console

   create a UI for managing environment variables and surfacing build error messages in the Firebase console (so you don't have to go into CloudBuild)

   16 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   started  ·  0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. apphosting for asia-northeast1 and asia-south1

   I am trying to deploy to asia-northeast1 and asia-south1

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Hosting  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. support SvelteKit in app hosting

   support SvelteKit apps in the new App Hosting

   15 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Allow to change the connected git repository from the console

   For a variety of reasons there are cases where the name of the repository (or organization, so the name too) changes, or we need to change the connected repository. Currently, this will require to create a new backend to configure it all over again.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Hosting  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Fix GitHub integration

    Issues:

    1. In the app hosting wizard: Connecting a GitHub account that is not the owner of the GitHub repository and then removing it breaks the GitHub integration process and the App Hosting set up process.
    2. Being just a collaborator to a GitHub repo doesn't make it visible in the App Hosting Set Up wizard, you have to connect with the GitHub account of the owner of the repo.

    Error messages:

    1. Connection verification failed: unable to verify the authorization token: GET https://api.github.com/user: 401 Bad credentials []: failed precondition.
    2. Error: Request to https://developerconnect.googleapis.com/v1/projects/PROJECT-ID/locations/europe-west4/connections/firebase-app-hosting-github-oauth:fetchGitHubInstallations had HTTP Error: 400, Failed to list GitHub installations

    I described the issue in detail in this r/Firebase reddit post:
    .

    https://www.reddit.com/r/Firebase/comments/1i1k4ln/firebase_app_hosting_and_github_issue/

    .

    Improvement suggestions:

    1. Don't make the GitHub integration step mandatory as I only wanted to manually deploy at that stage.

    2. Let the user know he needs to be the owner and can't change the "bot-account" later.

    3. Add the ability to remove the account and change to another.

    4. Make it work not only with repos where you are the owner but also to repos where you are collaborator

    5. Add the ability to "Factory reset" a firebase project.

    6. Add the ability to reuse a project ID if it's been deleted already.

    Issues:

    1. In the app hosting wizard: Connecting a GitHub account that is not the owner of the GitHub repository and then removing it breaks the GitHub integration process and the App Hosting set up process.
    2. Being just a collaborator to a GitHub repo doesn't make it visible in the App Hosting Set Up wizard, you have to connect with the GitHub account of the owner of the repo.

    Error messages:

    1. Connection verification failed: unable to verify the authorization token: GET https://api.github.com/user: 401 Bad credentials []: failed precondition.
    2. Error: Request to https://developerconnect.googleapis.com/v1/projects/PROJECT-ID/locations/europe-west4/connections/firebase-app-hosting-github-oauth:fetchGitHubInstallations had HTTP Error: 400, Failed to list GitHub installations

    … more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Flutter support for App Hosting

    Allow Firebase App Hosting to build and deploy Flutter apps.

    10 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  App Hosting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Support Functions on App Hosting

    Firebase Functions don't seem to be well supported in App Hosting. At least if you are using Typescript in the functions, the deploy process runs into an error in the build step. It seems to be because "npm run build" runs Typescript checking everywhere, and the dependencies in functions/package.json haven't been installed.

    A user on Stack Overflow who asked about this ended up working around it by setting tsconfig.json to ignore the functions directory. They also have to do a manual deploy of the functions, because apparently the App Hosting deploy process doesn't do it.

    Ideally everything should just work; type checking in functions would happen separately from the next.js code, and functions would get deployed automatically.

    Here's the error from the build process:

    Running "npm run build"

    chatfront@0.1.0 build
    next build
    Attention: Next.js now collects completely anonymous telemetry regarding usage.
    This information is used to shape Next.js' roadmap and prioritize features.
    You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
    https://nextjs.org/telemetry
    ▲ Next.js 15.2.1
    Creating an optimized production build ...
    ✓ Compiled successfully
    Linting and checking validity of types ...
    Failed to compile.
    ./functions/src/index.ts:10:25
    Type error: Cannot find module 'firebase-functions/v2/https' or its corresponding type declarations.
    8 | */
    9 |
    10 | import {onRequest} from "firebase-functions/v2/https";
    | ^
    11 | import * as logger from "firebase-functions/logger";
    12 |
    13 | // Start writing functions
    Next.js build worker exited with code: 1 and signal: null
    Done "npm run build" (29.986122243s)

    Firebase Functions don't seem to be well supported in App Hosting. At least if you are using Typescript in the functions, the deploy process runs into an error in the build step. It seems to be because "npm run build" runs Typescript checking everywhere, and the dependencies in functions/package.json haven't been installed.

    A user on Stack Overflow who asked about this ended up working around it by setting tsconfig.json to ignore the functions directory. They also have to do a manual deploy of the functions, because apparently the App Hosting deploy process doesn't do it.

    Ideally everything should just work;… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  App Hosting  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Turborepo support for Next.js apps

    AppHosting now supports nx based monorepo but we would love to see turborepo + pnpm workspace support for AppHosting.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  App Hosting  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. custom remote git support

    Support for self hosted gitlab or other git remote sources

    11 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Cloud Armor or WAF Support

    Enhanced security features such as Cloud Armor or WAF is almost a must-have nowadays also the level of protection is unclear.

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Custom build command

    It can be necessary to run a script before the build command.

    Example:

    • With angular: A script to create the environment.ts files need to be run before the ng build.
    • With Prisma: A script to generate the prisma files should be run before the build the build itself.

    Suggestion:

    As for render.com, get in the settings Build Command options and Start Command

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    started  ·  1 comment  ·  App Hosting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. VueJS support for App Hosting

    Allow Firebase App Hosting to support VueJS framework

    9 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Firebase project config in env

    Cloud functions do provide process. env.FIREBASE_CONFIG.

    One can set it in the yaml, but it would be nice if app hosting would provide these automatically.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  App Hosting  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Allow rewrite for hostname/domain (not only paths)

    It would be great to have the ability to redirect multiple domains to the same project.

    I tried to achieve this with regular expression redirect, but it doesn't work:

    {
            "regex": "https:\\/\\/.*?(?P<hostname>\\w+\\.[a-z]+)\\/",
            "destination": "/:hostname/index.html"
    }
    

    For example with domains one.com and two.com, I want to be able to redirect them to the same project but different subfolders (e.g. /one.com/index.html, /two.com/index.html) -- this will allow to share common resources (styles, images, etc) between the projects, while still being able to customize the content for each one.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  App Hosting  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Support submodules

    Support submodules for automated builds.

    Currently, builds fail when checking out submodules.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  App Hosting  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating