Deployment and operations
Production configuration, security boundaries, caches and recovery checks.
Provision the host
- Deploy a server-capable Next.js application with the Pagiera backend mounted.
- Provide PostgreSQL and Redis URLs through server-only configuration.
- Configure OpenRouter only if AI generation is needed.
- Protect editor, mutation and preview routes with host authentication and authorization.
- Check health, save, preview and public rendering in the target environment.
Publishing a page updates application data; it does not deploy the host application or provision infrastructure.
Server configuration
| Option | Purpose |
|---|---|
| postgresUrl | PostgreSQL connection |
| redisUrl | Redis connection |
| openRouterApiKey / openRouterModel | AI provider configuration |
| basePath | Mounted API base path |
| aiRateLimitPerMinute | AI request limit |
| templateRegistryUrl | Template registry upstream |
| allowPrivateHosts | Explicit private data-source host exceptions |
| maxSourceBytes | Maximum source response size; default 2 MB |
| mcpServers / authorizeMcp | Operator-owned MCP connections and authorization |
Use the server type definitions for exact signatures. Do not expose private host exceptions or MCP command configuration as public user input.
Data and cache lifecycle
PostgreSQL is persistent storage. Redis participates in published-page caching, template caching and rate limiting. Back up the database; do not treat a cache as your recovery copy. Test publishing and unpublishing through the runtime to catch stale content behavior in your deployment.
Release checklist
Verify unauthorized requests are rejected, secrets stay server-side, draft routes stay private, data-source failures behave predictably, and backups can be restored. Monitor database connectivity, request errors and AI provider failures without logging credentials. Read security before production.