Running Seed
This is the starting page for people who run Seed software for others, and it says what you can run, which page to read first, and what each operations page is for.

Welcome. This section is for people who run Seed software for others: a site, an app environment, or the services beside them. It says what you can run, which page to read first, and what each page is for. If you only want to use Seed, you do not need any of this.

Is something broken right now? Go to troubleshooting for an app environment, to seed-deploy doctor in self-hosting for a site, or to daemon operations for a slow daemon.

What can be run


    A site. A site shows one space at a web domain. It is a daemon and a web app behind a reverse proxy. This is what most operators run. Sites explains what a site is in the protocol.

    An app environment. The server that runs agents and apps. It can run beside a site, alone, or inside the desktop app. See the app environment program map.

    The vault. The service that keeps the keys of people's accounts and signs them in. A site uses the hosted vault, unless it is an enterprise node. See the vault program map.

    Notify. The service that keeps notification inboxes and sends email. A site uses the hosted one, unless it is an enterprise node. See the notify program map.

The software section has one map page for each program. It says where the code is, what the program listens on, and how you configure it.

Reading order


    Self-hosting, to set up a site and learn the seed-deploy command.

    Operations, if the site runs an app environment or you run one alone. It leads to every app environment page.

    Troubleshooting, when something is wrong.

If you are setting up a closed node for one organization, read the enterprise node page in place of step 2.

Sites

App environment

See also

Sites and nodes

Running an app environment

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime

People