Static Hosting Terbium

July 20, 2026 · View on GitHub

Last Updated: v2.4.0 - 07/16/2026

This guide covers deploying Terbium to static hosting platforms. For this tutorial, Cloudflare Pages will be used, however the instructions will be similar on other static hosts.

Step 1: Fork and Connect Repository

Fork this repository and connect your GitHub account to the static host of your choice.

⚠️ NOTE: On Cloudflare Pages, Terbium is automatically configured to use Node 20. If you're using a different host, check with them that you are using Node 20 or later, as Terbium WILL NOT build on older versions.

Step 2: Configure Build Settings

Under the build section command, enter:

npm i; npm run build-static

LEAVE THE START COMMAND BLANK IF IT EXISTS

Then under the output directory, enter: dist

Click Deploy to start the build process.

Step 3: Configure Wisp Server (Optional)

Now that the site is deployed, you have probably noticed that the default Wisp server won't be running since you're on static hosting.

Option 1: Configure during OOBE
You can configure the Wisp server URL during the Out-of-Box Experience (OOBE) when you first load Terbium.

Option 2: Hardcode before deployment
If you wish to set a default Wisp server before deployment:

  1. Navigate to src/init/index.ts
  2. Find the Wisp server configuration (around line 41)
  3. Replace the default expression: 
    `${location.protocol.replace("http", "ws")}//${location.hostname}:${location.port}/wisp/`
    With your Wisp server URL as a string: 
    "wss://your-wisp-server.example.com/wisp/"