From bb202be12cadc7f2ff8974d3ac13d5d9f2afeff7 Mon Sep 17 00:00:00 2001 From: Reynaldi Chernando <12949382+reynaldichernando@users.noreply.github.com> Date: Wed, 10 Jun 2026 23:04:42 +0700 Subject: [PATCH] Minor clarification local webserver in deployment (#3247) --- src/docs/src/deployments.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/docs/src/deployments.md b/src/docs/src/deployments.md index 2c913ae94..529e87551 100644 --- a/src/docs/src/deployments.md +++ b/src/docs/src/deployments.md @@ -9,9 +9,9 @@ Puter.js is a regular JavaScript library, so your app deploys like any other web ## Deploy anywhere -Because Puter.js runs entirely in the browser, there's no special backend to provision. Build your app as you normally would and serve the output from any static or web hosting provider, such as Vercel, Cloudflare Pages, Netlify, or GitHub Pages. +Because Puter.js runs entirely in the browser, there's no special backend to provision. Build and serve your app the same way you would any other website, on any hosting provider, such as Vercel, Cloudflare Pages, Netlify, or GitHub Pages. -
Your app should be served by a web server, like any of the hosting providers above.
+
The only requirement is that the app is served by a web server. A hosting provider, a self-hosted server, and a local development server are all valid. Opening the HTML file directly from disk does not work.
No extra configuration is required. Your app keeps talking to Puter's services from the browser, wherever it's hosted. @@ -66,7 +66,7 @@ Then deploy your site's directory to a `*.puter.site` subdomain: puter site deploy [dir] [subdomain] ``` -Both arguments are optional — run `puter site deploy` with no arguments and the CLI prompts you for the directory and subdomain. +Both arguments are optional: run `puter site deploy` with no arguments and the CLI prompts you for the directory and subdomain.
The Puter CLI is currently in beta (0.x), so commands and behavior may change.