Skip to content

Commit ef1a9ec

Browse files
docs: add a "How to deploy" section to the App Hosting guide
Links Firebase's own deploy guides for the two public paths (connect a GitHub repo, or firebase deploy from a local machine) instead of re-documenting the steps, so the guide's title is honest and the reader reaches the deploy instructions before the Angular-specific gotcha.
1 parent 6388192 commit ef1a9ec

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

‎docs/app-hosting.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,10 @@
88

99
This guide covers one thing that trips up almost every new SSR deployment: **the server can silently stop server-rendering and fall back to client-side rendering (CSR), with no error anywhere obvious.** It explains how to detect that in 30 seconds and how to fix it.
1010

11+
## How to deploy
12+
13+
If you have not deployed yet, follow Firebase's own guides: [Get started with App Hosting](https://firebase.google.com/docs/app-hosting/get-started) to connect a GitHub repository (App Hosting builds and deploys on every push), or [Alternative ways to deploy](https://firebase.google.com/docs/app-hosting/alt-deploy) to deploy with `firebase deploy` from your own machine. Both build your app the same way in Google Cloud Build. The rest of this guide covers an Angular-specific issue you can hit once your app is deployed either way.
14+
1115
## The symptom: SSR silently downgrades to CSR
1216

1317
A freshly deployed Angular SSR app usually *looks* fine in a browser, the page renders and works. But the server may be sending an almost-empty HTML shell and letting the browser do all the rendering. When that happens you lose the whole point of SSR: crawlers and link previews see no content, and first paint on slow devices is worse.

0 commit comments

Comments
 (0)