Publish

Publishing puts a workspace’s static build at https://<name>.serin.work. The site stays up while the server sleeps.

How to publish

From the app. Choose Publish in the preview’s toolbar or the command palette. Pick a name, then publish. Publishing again replaces what’s live.
From an agent. The publish tool runs the same build and upload. You approve each publish in the app.

A name is 3 to 40 lowercase letters, digits and hyphens. Anyone with the address can see the site.

What gets published

If publish.command is set in .serin/serin.json, it runs. Otherwise the build script in package.json runs with the project’s package manager. Packages are installed first when node_modules is missing.
The site is publish.dir, or the first of these folders with an index.html. With no build, a workspace with an index.html at its root publishes as it is.

Framework	Folder
Next.js	`out` (needs `output: 'export'` in `next.config`)
Vite, Astro, Vue CLI, Parcel	`dist`
Angular	`dist`, including `dist/<project>/browser`
SvelteKit, Create React App, Docusaurus	`build`
Remix, React Router	`build/client`
Nuxt	`.output/public`, then `dist`
Gatsby	`public`
Eleventy	`_site`

Static files only. No server code runs on the site.
Files and folders starting with a dot are left out, apart from .well-known, and so are node_modules and .git.
A site can have up to 5,000 files and 200 MB, with no file over 25 MB. A build still running after 15 minutes is stopped.
With spa on, unknown paths get /index.html, for apps that route in the browser.

Roll back

At serin.work, open Account. Under Published sites, choose Deploys next to a site. Every deploy is listed with its files, size and where it came from. Roll Back makes an earlier one live again. Delete takes the site down.