Deployment & Sharing

Download Your Code & GitHub

Your app's code is yours. You can download it as a standard Vite project, or have Webase push every version to a GitHub repository. Either way, the app's data stays on Webase.

Download the Code

1

Open the Publish Menu

Click Publish in the editor's header. Find the Your code section.

2

Click Download the code

Your browser downloads a zip named after your app, such as my-task-manager.zip. It holds the latest draft of your code, whether or not you've published it.

3

Run It

Unzip it, then in a terminal:

npm install
npm run dev

npm run build writes a static site to dist/. It uses relative paths and hash URLs, so any static host can serve it from any folder, with no rewrite rules.

What's in the Zip

  • src/ — your app as Webase wrote it. Imports from esm.sh become npm packages, listed in package.json.
  • index.html — loads Tailwind from its CDN, with its config inline. There's no Tailwind build step.
  • README.md — how to run and build the project.
  • .env.example — the Webase server the app talks to.

Your Data Stays on Webase

The code leaves Webase. The data doesn't. The downloaded app still stores records, signs people in, uploads files and makes AI calls through your Webase server, under the same app.

  • Keep the app on Webase. If you delete it there, the downloaded copy stops working.
  • Download again after changing data models. The code refers to your models and fields by ID. If you add or change them in Webase, export a fresh copy.
  • To use another Webase server, copy .env.example to .env and set VITE_WEBASE_API_URL.

Push Every Version to GitHub

Connect a GitHub repository and Webase pushes each new version of your app to it as a commit. The repository holds the same standalone Vite project as the download.

1

Connect GitHub

Open the Settings tab and find GitHub. Click Connect GitHub and approve access on GitHub. You come back to Settings.

2

Create a Repository

Webase suggests a name under New repository name. Change it if you like. Private repository is checked by default. Click Create repository.

Webase creates the repository and pushes your latest version as the first commit.

3

Keep Building

From then on, every new version is pushed as its own commit: chat changes, code saves, Test fixes, restores and theme changes. The commit message is the version's summary. The GitHub section shows the repository and the last push, like Last pushed v14 · 3 minutes ago.

Pushing only goes one way. Webase pushes to the repository but never brings changes back. If you edit files on GitHub, the next push replaces them with the app's code. Your edits stay in the repository's history.

Managing the Connection

  • Push now — push any versions that haven't gone yet. After a failed push, the button says Try again.
  • Reconnect GitHub — appears if GitHub stops accepting Webase's access. Pushes pause until you reconnect.
  • Unlink — stops pushing to the repository. The repository stays on GitHub.
  • Disconnect — next to Connected as @your-name. Webase forgets your GitHub access, for all your apps. Pushes stop until you connect again.

The Publish menu also shows where versions go: Every version is also pushed to your repository.

If You Don't See the GitHub Section

The GitHub section only appears when your Webase instance has a GitHub OAuth App set up. Admins see a note saying GitHub isn't set up on this instance, with the steps:

  1. Register a GitHub OAuth App with the callback URL your-webase-host/github/callback.
  2. Set GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET on the server.

Webase asks GitHub for the repo scope, so it can create private repositories. Set GITHUB_OAUTH_SCOPE=public_repo to ask for less. People then need to uncheck Private repository when they create one.