Guides

Several sites in one deployment

Serve more than one site from one Hollware, with their own collections, tokens and people.

Several sites in one deployment

One Hollware serves every site of its config. Each site has its own collections, entries, tokens and members; nothing crosses from one to another.

Add a site

Add it to hollware.config.ts:

export default defineConfig({
  sites: {
    blog: { ... },
    docs: {
      locales: ['en'],
      defaultLocale: 'en',
      collections: { docs },
    },
  },
})

Deploy, then create it in the database. When the database has an owner, init makes that owner the owner of the new site too, and prints a token of it:

npm run deploy
npx hollware init --site docs --remote

Tokens and grants

A token belongs to one site and acts on it alone, whatever it asks for. An agent that writes to two sites has two tokens, or two OAuth grants. A site that reads over the service binding names its site in each call.

People

A person is one across the deployment, with one passkey. Their role is per site: an author of the blog can be an editor of the docs.

Note
An invitation always makes a new person for now. Someone who is already a member of one site and is invited to another sets up a second passkey for it.

This site is one: hollware.com reads its docs from the same Hollware as the demo blog.