docs: merge deployment pages in getting started

docs/content/1.getting-started/10.deployment.md

@@ -0,0 +1,141 @@
+# Deployment
+
+A Nuxt application can be deployed on a Node or Deno server, pre-rendered to be hosted in static environments, or deployed to serverless and edge providers.
+
+## Node.js Server
+
+Discover the Node.js server preset with Nitro to deploy on any Node hosting.
+
+::list
+
+- **Default output format** if none is specified or auto-detected <br>
+- Loads only the required chunks to render the request for optimal cold start timing <br>
+- Useful for deploying Nuxt apps to any Node.js hosting
+::
+
+### Entry Point
+
+When running `nuxt build` with the Node server preset, the result will be an entry point that launches a ready-to-run Node server.
+
+```bash
+node .output/server/index.mjs
+```
+
+### Example
+
+```bash
+$ node .output/server/index.mjs
+Listening on http://localhost:3000
+```
+
+### Configuring Defaults at Runtime
+
+This preset will respect the following runtime environment variables:
+
+- `NITRO_PORT` or `PORT` (defaults to `3000`)
+- `NITRO_HOST` or `HOST` (defaults to `'0.0.0.0'`)
+- `NITRO_SSL_CERT` and `NITRO_SSL_KEY` - if both are present, this will launch the server in HTTPS mode. In the vast majority of cases, this should not be used other than for testing, and the Nitro server should be run behind a reverse proxy like nginx or Cloudflare which terminates SSL.
+
+#### Using PM2
+
+To use `pm2`, use an `ecosystem.config.js`:
+
+```js [ecosystem.config.js]
+module.exports = {
+  apps: [
+    {
+      name: 'NuxtAppName',
+      exec_mode: 'cluster',
+      instances: 'max',
+      script: './.output/server/index.mjs'
+    }
+  ]
+}
+```
+
+#### Using Cluster Mode
+
+You can use `NITRO_PRESET=node_cluster` in order to leverage multi-process performance using Node.js [cluster](https://nodejs.org/dist/latest/docs/api/cluster.html) module.
+
+By default, the workload gets distributed to the workers with the round robin strategy.
+
+### Learn More
+
+:ReadMore{link="https://nitro.unjs.io/deploy/node" title="the Nitro documentation for node-server preset"}
+
+## Static Hosting
+
+There are two ways to deploy a Nuxt application to any static hosting services:
+
+- Static site generation (SSG) prerenders every route of your application at build time. For every page, Nuxt uses a crawler to generate a corresponding HTML and payload files.
+- Using `ssr: false` to produce a pure client-side output.
+
+### Prerendering
+
+Use the [`nuxi generate` command](/api/commands/generate) to build your application. The HTML files will be generated in the `.output/public` directory.
+
+```bash
+npx nuxi generate
+```
+
+### Client-side Only Rendering
+
+If you don't want to prerender your routes, another way of using static hosting is to set the `ssr` property to `false` in the `nuxt.config` file. The `nuxi generate` command will then output an `index.html` entrypoint like a classic client-side Vue.js application.
+
+```ts [nuxt.config.ts|js]
+defineNuxtConfig({
+  ssr: false
+})
+```
+
+### Advanced
+
+You can manually specify routes that [Nitro](/guide/concepts/server-engine) will fetch and prerender during the build.
+
+```ts [nuxt.config.ts|js]
+defineNuxtConfig({
+  nitro: {
+    prerender: {
+      routes: ['/user/1', '/user/2']
+    }
+  }
+})
+```
+
+## Presets
+
+In addition to Node.js servers and static hosting services, a Nuxt 3 project can be deployed with several well-tested presets and minimal amount of configuration.
+
+You can use the [Nuxt config](/guide/directory-structure/nuxt.config) to explicitly set the preset to use:
+
+```js [nuxt.config.js|ts]
+export default {
+  nitro: {
+    preset: 'node-server'
+  }
+}
+```
+
+Or directly use the `NITRO_PRESET` environment variable when running `nuxt build`:
+
+```bash
+NITRO_PRESET=node-server nuxt build
+```
+
+🔎 Check [the Nitro deployment](https://nitro.unjs.io/deploy) for all possible deployment presets and providers.
+
+### Supported Hosting Providers
+
+Nuxt 3 can be deployed to several cloud providers with a minimal amount of configuration:
+
+- :IconCloud{class="h-5 w-4 inline mb-2"} [AWS](https://nitro.unjs.io/deploy/providers/aws)
+- :LogoAzure{class="h-5 w-4 inline mb-2"} [Azure](https://nitro.unjs.io/deploy/providers/azure)
+- :LogoCloudFlare{class="h-5 w-4 inline mb-2"} [CloudFlare](https://nitro.unjs.io/deploy/providers/cloudflare)
+- :IconCloud{class="h-5 w-4 inline mb-2"} [Digital Ocean](https://nitro.unjs.io/deploy/providers/digitalocean)
+- :LogoFirebase{class="h-5 w-4 inline mb-2"} [Firebase](https://nitro.unjs.io/deploy/providers/firebase)
+- :IconCloud{class="h-5 w-4 inline mb-2"} [heroku](https://nitro.unjs.io/deploy/providers/heroku)
+- :IconCloud{class="h-5 w-4 inline mb-2"} [layer0](https://nitro.unjs.io/deploy/providers/layer0)
+- :LogoNetlify{class="h-5 w-4 inline mb-2"} [Netlify](https://nitro.unjs.io/deploy/providers/netlify)
+- :IconCloud{class="h-5 w-4 inline mb-2"} [Render](https://nitro.unjs.io/deploy/providers/render)
+- :IconCloud{class="h-5 w-4 inline mb-2"} [Stormkit](https://nitro.unjs.io/deploy/providers/stormkit)
+- :LogoVercel{class="h-5 w-4 inline mb-2"} [Vercel](https://nitro.unjs.io/deploy/providers/vercel)