docs: deployment instructions with routeRules

Author: posva

docs/nuxt/deployment.md

@@ -2,23 +2,50 @@
 
 > This section is a work in progress.
 
-It is recommended not to SSR every route in your application. Instead, you should only SSR or SSG (generate at build) the routes that are critical for SEO and performance. For example, you can SSG the homepage and the product pages, but not the cart page or profile pages.
+## Spark plan
 
-You can achieve this by combining the [`prerender` option for nitro](https://nuxt.com/docs/getting-started/deployment#selective-pre-rendering):
+The Spark plan is a free plan that enable most of firebase services. With this plan, you want to **prerender your app and deploy it as a static site**. In order to do this, make sure **not to apply the Firebase preset** when bundling your app and to use the `generate` command:
 
-```ts
-// nuxt.config.ts
-defineNuxtConfig({
+```sh
+nuxt generate
+```
+
+You can then let your CI deploy your app to Firebase or do it manually:
+
+```sh
+firebase deploy
+```
+
+Note that this requires `ssr: true` in your `nuxt.config.ts` but you can also use `ssr: false` and deploy your Nuxt app as a Single Page Application to Firebase Hosting. In that case you should run `nuxt build` instead of `nuxt generate` as the latter requires SSR.
+
+## Blaze plan
+
+::: warning
+The Firebase preset is still experimental. It is not recommended to use it in production.
+:::
+
+The Blaze plan is a pay-as-you-go that allows you to run Firebase Functions. **It is free up to a certain amount of requests**. With this plan, you can either do the same as with the [Spark plan](#spark-plan) (cheaper) or build with the Firebase preset and deploy your app as a serverless function:
+
+```sh
+NITRO_PRESET=firebase nuxt build
+```
+
+alternatively, you can use the `nitro.preset` option in your `nuxt.config.ts`, which will only be applied during builds.
+
+```ts{3}
+export default defineNuxtConfig({
   nitro: {
-    prerender: {
-      routes: ['/', '/products'],
-    },
+    preset: 'firebase',
   },
-  //
+  // ...
 })
 ```
 
-and the [`routeRules` option](https://nuxt.com/docs/guide/concepts/rendering#hybrid-rendering) to enable Hybrid rendering:
+### Route Rules
+
+On top of prerendering any routes, you can also use [the `routeRules` option](https://nuxt.com/docs/guide/concepts/rendering#hybrid-rendering) to apply any headers like cache options, redirects or even static rendering.
+
+It is recommended **not to SSR** every route in your application. Instead, you should only SSR or SSG (generate at build) the routes that are critical for SEO and performance. For example, you can SSG the homepage and the product pages, but not the cart page or the admin dashboard. Here is an example of a `routeRules` configuration:
 
 ```ts
 // nuxt.config.ts
@@ -37,21 +64,7 @@ defineNuxtConfig({
 })
 ```
 
-## Spark plan
-
-The Spark plan is a free plan that enable most of firebase functions. With this plan, you want to **prerender your app and deploy it as a static site**. In order to do this, make sure **not to apply the Firebase preset** when bundling your app and to use the `generate` command:
-
-```sh
-nuxt generate
-```
-
-You can then let your CI deploy your app to Firebase or do it manually:
-
-```sh
-firebase deploy
-```
-
-### Nitro Preset
+### Custom Nitro Preset
 
 To customize the Firebase functions configuration, it's recommended to create your own _nitro preset_ instead of using the `firebase` preset.
 
@@ -100,19 +113,3 @@ export default defineNuxtConfig({
 ```
 
 Make sure you **don't have** a `nitro.preset` option set in your `nuxt.config.ts` file.
-
-## Blaze plan
-
-::: warning
-The Firebase preset is still experimental. It is not recommended to use it in production.
-:::
-
-The Blaze plan is a pay-as-you-go that allows you to run Firebase Functions. It's free up to a certain amount of requests. With this plan, you can either do the same as with the [Spark plan](#spark-plan) (cheaper) or build with the Firebase preset and deploy your app as a serverless function:
-
-```sh
-NITRO_PRESET=firebase nuxt build
-```
-
-### Route Rules
-
-On top of prerendering any routes, you can also use [the `routeRules` option](https://nuxt.com/docs/api/configuration/nuxt-config#routerules-1) to apply any headers like cache options, redirects or even static rendering.

firestore.rules

@@ -4,6 +4,21 @@ service cloud.firestore {
     match /__tests/{document=**} {
       allow read, write;
     }
+
+    match /todos/{todoId} {
+      allow read, write;
+    }
+    match /tweets/{todoId} {
+      allow read, write;
+    }
+    match /users/{todoId} {
+      allow read: if request.auth.uid != null;
+      allow write: if false;
+    }
+    match /configs/jORwjIykFo2NmkdzTkhU {
+      allow read, write;
+    }
+
     match /{document=**} {
       allow read, write: if false;
     }