Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://firebase.google.com/docs/hosting/quickstart below:

Get started with Firebase Hosting

Stay organized with collections Save and categorize content based on your preferences.

Firebase Hosting gives you a fast, secure, and reliable way to host your app's static assets (HTML, CSS, JavaScript, media files, etc.) as well as to serve dynamic content and host microservices.

Our production-grade hosting is backed by a global content delivery network (CDN). Hosting serves your content over SSL, by default, and can be used with your own custom domain or on your project's subdomains at no cost on web.app and firebaseapp.com.

Before you can set up Firebase Hosting, you need to create a Firebase project.

Visit the Firebase CLI documentation to learn how to install the CLI or update to its latest version.

To connect your local project files to your Firebase project, run the following command from the root of your local project directory:

firebase init hosting

During project initialization, from the Firebase CLI prompts:

1. Select a Firebase project to connect to your local project directory.

   The selected Firebase project is your "default" Firebase project for your local project directory. To connect additional Firebase projects to your local project directory, set up project aliases.

2. Specify a directory to use as your public root directory.

   This directory contains all your publicly served static files, including your index.html file and any other assets that you want to deploy to Firebase Hosting.

   • The default for the public root directory is called public.

     • You can specify your public root directory now or you can specify it later in your firebase.json configuration file.

     • If you select the default and don't already have a directory called public, Firebase creates it for you.

   • If you don't already have a valid index.html file or 404.html file in your public root directory, Firebase creates them for you.

3. Choose a configuration for your site.

   If you select to make a one-page app, then Firebase automatically adds rewrite configurations for you.

At the end of initialization, Firebase automatically creates and adds two files to the root of your local app directory:

• A firebase.json configuration file that lists your project configuration. Learn more about this file on the configure hosting behavior page.

• A .firebaserc file that stores your project aliases.

To deploy to your site, run the following command from the root of your local project directory:

firebase deploy --only hosting

This command deploys your Hosting content and config to the following Firebase-provisioned subdomains:

• PROJECT_ID.web.app
• PROJECT_ID.firebaseapp.com

Learn more about deploys and even locally testing your site.

Now your site is ready to share with the world!

• Continue to improve your site. Test locally, share changes at a temporary preview URL, then deploy to your live site. Follow this step-by-step guide.

• Learn about further hosting capabilities:

  • Configure hosting behavior
  • Connect a custom domain
  • Serve dynamic content and host microservices

• Take a look at the full documentation for the Firebase CLI.

• Prepare to launch your app:

  • Set up budget alerts for your project in the Google Cloud console.
  • Monitor the Usage and billing dashboard in the Firebase console to get an overall picture of your project's usage across multiple Firebase services. You can also visit the Hosting Usage dashboard for more detailed usage information.
  • Review the Firebase launch checklist.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-15 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-15 UTC."],[],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4