Skip to main content
The Recipe Registry Server provides an HTTP interface for sharing recipes across teams and organizations. It supports token-based authentication, read-only mode, and can be deployed locally or on cloud infrastructure.
praisonai serve registry is the canonical command. The legacy praisonai registry serve form is deprecated (prints a warning to stderr) and its default port is now 7777 — aligned with this form. Update any old scripts or Dockerfiles that relied on the old 8080 default. See the Registry CLI for details.

Quick Start

Server Configuration

Basic Server

Authentication

Enable token authentication to protect write operations:

Read-Only Mode

Deploy a read-only registry for public access:

Programmatic Server

Start the server programmatically in Python:

WSGI Application

Get the WSGI app for custom deployment:

Health Check

Check server status:
Response:

Deployment Options

Local Development

Docker

Docker Compose

Kubernetes

Behind Nginx

Security Best Practices

Token Management

Network Security

  • Local only: Bind to 127.0.0.1 for local-only access
  • Firewall: Restrict port access to trusted IPs
  • TLS: Use nginx/traefik for HTTPS termination
  • VPN: Deploy within private network

Access Control

Monitoring

Logs

Server logs include:
  • Request method and path
  • Response status codes
  • Authentication attempts
  • Error details

Metrics

Monitor these endpoints:
  • GET /healthz - Health check
  • GET /v1/recipes - Recipe count

Environment Variables

Troubleshooting

Port Already in Use

Permission Denied

Authentication Errors