Multiple site hosting in Firebase - Step-by-Step Execution

Process Flow - Multiple site hosting

Start: Prepare sites

↓

Create firebase.json config

↓

Add hosting targets for each site

↓

Run firebase deploy

↓

Firebase uploads each site

↓

Sites available at different URLs

↓

Users access sites separately

This flow shows how you prepare multiple sites, configure them in Firebase, deploy, and then access each site at its own URL.

Execution Sample

Firebase

firebase init hosting
firebase.json with multiple targets
firebase deploy --only hosting:site1,hosting:site2

This sequence initializes hosting, configures multiple sites, and deploys them to Firebase.

Process Table

Step	Action	Input/Config	Result	Notes
1	Initialize Firebase Hosting	firebase init hosting	Hosting setup files created	Prepares project for hosting
2	Edit firebase.json	{ "hosting": [{"target": "site1", "public": "site1"}, {"target": "site2", "public": "site2"}] }	Multiple hosting targets defined	Configures multiple sites
3	Deploy sites	firebase deploy --only hosting:site1,hosting:site2	Site1 and Site2 uploaded	Deploys both sites in one command
4	Access sites	site1 URL and site2 URL	Each site loads separately	Users see different content per site
5	Exit	All sites deployed	Deployment complete	No errors, hosting active

💡 All sites deployed and accessible at their respective URLs

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
firebase.json	empty or default	configured with multiple hosting targets	unchanged	configured with multiple hosting targets
hosting targets	none	site1 and site2 defined	site1 and site2 deployed	site1 and site2 deployed
deployment status	not deployed	not deployed	deployed	deployed

Key Moments - 3 Insights

Why do we need to specify multiple hosting targets in firebase.json?

Because each site needs its own configuration to tell Firebase where its files are and how to serve it. See execution_table step 2.

Can we deploy multiple sites with one command?

Yes, using 'firebase deploy --only hosting:site1,hosting:site2' deploys all specified sites at once. See execution_table step 3.

How do users access different sites after deployment?

Each site has its own URL or subdomain configured by Firebase, so users visit different addresses to see each site. See execution_table step 4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result after editing firebase.json in step 2?

A Sites deployed

B Multiple hosting targets defined

C Hosting setup files created

D Users access sites

💡 Hint

Check the 'Result' column in step 2 of execution_table

At which step are the sites actually uploaded to Firebase?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look for 'uploaded' or 'deployed' in the 'Result' column

If we only deploy hosting:site1, what happens to site2?

A Site2 remains unchanged and not updated

B Site2 is also deployed automatically

C Site2 is deleted

D Deployment fails

💡 Hint

Refer to deployment command in execution_sample and step 3 in execution_table

Concept Snapshot

Multiple site hosting in Firebase:
- Define multiple hosting targets in firebase.json
- Each target points to a different folder
- Deploy multiple sites with one command
- Each site gets its own URL
- Users access sites separately

Full Transcript

Multiple site hosting in Firebase involves preparing each site folder, configuring firebase.json with multiple hosting targets, and deploying them together. The process starts by initializing hosting, then editing firebase.json to add each site as a target with its own public folder. Deployment uploads all specified sites, making them available at separate URLs. Users can then access each site independently. This method allows managing multiple websites under one Firebase project efficiently.