Running Peperossa

These pages are for whoever runs Peperossa for an organisation: installing it, giving teams and systems their API keys, sharing the renderers fairly, measuring use and keeping it healthy. If someone else runs Peperossa for you, you need none of them: start with designing a template or rendering from the API.

• How Peperossa is put together: the services and what each keeps.
• Install: from the image and its Compose file to a first API key.
• Storage and the database: what is kept where, for how long, and what to back up.
• Tenants and API keys: the admin API.
• Security: what keeps tenants apart, and what to keep off the internet.
• Scheduler and tiers: sharing the workers between tenants.
• Metering: what each tenant used.
• Fonts and their rights: which fonts may be used, and how that is recorded.
• Upgrading: a new image without surprises in the output.
• Troubleshooting: probes, logs and request ids.

Every setting is listed in the configuration reference.