Publishing

npx seemore build  # static export to dist/ for any host

The result is a dist/ folder of plain web files. Drop it on Netlify, Surge, Cloudflare Pages or GitHub Pages, or hand it to any web host. Every page is a separate index.html, next to a 404.html that every static host reads. seemore also writes the files each host needs: _redirects for Netlify and Cloudflare Pages, 200.html for Surge, .nojekyll for GitHub Pages.

This site is built the same way. See its seemore.config.ts and the features page for what publishing gives you by default.

Password protection

Protect a whole site with one shared password. No server or account is needed. Turn it on in seemore.config.ts:

// seemore.config.ts
export default {
  title: 'Acme Handbook',
  auth: true,
};

Keep the password out of the config file. seemore build reads it from the SEEMORE_PASSWORD environment variable. The build fails if the variable is missing:

SEEMORE_PASSWORD='a-long-passphrase' npx seemore build

On Windows PowerShell:

$env:SEEMORE_PASSWORD='a-long-passphrase'; npx seemore build

The build encrypts the site content and search index. The output is still a plain dist/ folder that you can deploy to any of the hosts above.

Staying unlocked

remember sets how long a visitor stays unlocked after their last visit. The default is one day:

auth: { remember: '12h' }  // hours
auth: { remember: '7d' }   // days

Renaming the site logs everyone out once. To avoid that, set a stable id. Changing id logs everyone out, just like changing the password:

auth: { id: 'acme-handbook' }