From 2b21022fb78299692c2f6294f012be1ec297e10f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nils=20Kr=C3=BCger?= Date: Wed, 8 Jan 2025 21:24:18 +0100 Subject: [PATCH] Fix typo in deploy guide (#383) --- docs-src/0.6/src/guide/deploy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs-src/0.6/src/guide/deploy.md b/docs-src/0.6/src/guide/deploy.md index 8c11a043..e5dec68d 100644 --- a/docs-src/0.6/src/guide/deploy.md +++ b/docs-src/0.6/src/guide/deploy.md @@ -32,7 +32,7 @@ Making native app distribution easier is a top priority for Dioxus Deploy! Dioxus web apps are structured as a Client bundle and a Server executable. Generally, any deploy provider that exposes a simple container will be sufficient for a Dioxus fullstack web application. -Some providers like [Cloudflare Workers](http://workers.cloudflare.com) and [Fermyon Spin](https://www.fermyon.com/spin) provider WASM-based containers for apps. WASM runtimes are typically cheaper to operate and can horizontally scale better than a traditional virtual-machine based container. When deploying on WASM runtimes, you will need to create a WASM build of your server manually. +Some providers like [Cloudflare Workers](http://workers.cloudflare.com) and [Fermyon Spin](https://www.fermyon.com/spin) provide WASM-based containers for apps. WASM runtimes are typically cheaper to operate and can horizontally scale better than a traditional virtual-machine based container. When deploying on WASM runtimes, you will need to create a WASM build of your server manually. Running the webserver is as simple as executing `./server`. Make sure to set the IP and PORT environment variables correctly: