Production Deployment Guide

Guide for deploying MetaPilot to production platforms (Render, Docker, Linux Systemd).

1. Docker Compose Deployment

MetaPilot provides pre-built Docker Compose configurations under

infrastructure/docker/

Launch Production Stack

bash

cd infrastructure/docker/production
docker-compose up -d --build

Stack Components

```
api
```
: Daphne ASGI application server (
```
port 8000
```
).
```
celery_worker
```
: Background campaign & message worker node (
```
concurrency=4
```
).
```
celery_beat
```
: Periodic cron scheduler daemon.
```
redis
```
: Redis server for task queues & Channels layer (
```
port 6379
```
).
```
postgres
```
: PostgreSQL 16 relational database (
```
port 5432
```
).

️ 2. Render Deployment

MetaPilot includes a

Procfile

for one-click deployment on Render:

text

web: daphne -b 0.0.0.0 -p $PORT core.asgi:application
worker: celery -A core worker -Q celery,scheduler,jobs --loglevel=info --concurrency=4
beat: celery -A core beat --scheduler django_celery_beat.schedulers:DatabaseScheduler --loglevel=info

Environment Variables Checklist on Render

```
SECRET_KEY
```
: Set to strong 64-character random string.
```
DEBUG
```
: Set to
```
False
```
.
```
ALLOWED_HOSTS
```
: Set to your Render hostname (e.g.
```
api.metapilot.in
```
).
```
FERNET_KEY
```
: Set to valid 32 url-safe base64-encoded key.
```
DATABASE_URL
```
: Linked PostgreSQL instance connection string.
```
CELERY_BROKER_URL
```
&
```
CHANNEL_REDIS_URL
```
: Linked Managed Redis connection strings.