Search code examples
firebasefirebase-hosting

Incremental deployments in a Firebase Hosting project


I have an static site with around 120K pages and a size of around 2GB deployed in a Firebase Hosting project, and this will grow.

All should be deployed in the same domain to be able to keep the user authenticated. Also, different modules are deployed in different paths but same domain (business requirements).

I'm thinking about the way to split the project to allow deployment of only small parts of the project, to avoid to deploy 2GB every day, when there are changes only on few MB of pages.

Is there a way to do incremental deployment in a Firebase Hosting project?

Any other idea?


Solution

  • It already does incremental deployments. Read the section near the end of this blog called "Your uploads just got a bit faster, and in some cases a lot faster".

    This new system only processes new, modified, or deleted files. You know, the delta. This means any files that are unchanged aren’t uploaded when you run firebase deploy. You may not notice a big improvement in performance if your site is only a few files. However, it will make a huge difference for sites with a large amount of existing unmodified assets.