Self-Hosting Overview

Self-Hosting Alita Robot

This guide covers everything you need to deploy your own instance of Alita Robot.

Prerequisites

Before you begin, ensure you have:

Component	Minimum Version	Purpose
PostgreSQL	14+	Primary database
Redis	6+	Caching layer
Docker (recommended)	20.10+	Container deployment

For building from source:

• Go 1.25+

Deployment Options

Docker Compose (Recommended)

The easiest way to deploy Alita. Includes PostgreSQL and Redis.

git clone https://github.com/divkix/Alita_Robot.git
cd Alita_Robot
cp sample.env .env
# Edit .env with your configuration
docker-compose up -d

Full Docker Guide →

Binary Deployment

Download pre-built binaries for your platform:

• Linux (amd64, arm64)
• macOS (amd64, arm64)
• Windows (amd64)

Binary Installation →

Build from Source

Compile the bot yourself:

git clone https://github.com/divkix/Alita_Robot.git
cd Alita_Robot
go build -o alita_robot .

Building from Source →

Essential Configuration

At minimum, you need these environment variables:

BOT_TOKEN=your_bot_token_from_botfather
OWNER_ID=your_telegram_user_id
MESSAGE_DUMP=-100xxxxxxxxxx  # Log channel ID
DATABASE_URL=postgres://user:pass@host:5432/db
REDIS_ADDRESS=localhost:6379

Full Environment Reference →

Webhook vs Polling

Mode	Use Case	Setup Complexity
Webhook	Production	Requires HTTPS domain
Polling	Development	Simple, works anywhere

Webhook Setup →

Database Setup

Alita uses PostgreSQL with automatic migrations:

# Enable auto-migration
AUTO_MIGRATE=true

# Or run manually
make psql-migrate

Database Guide →

Monitoring

Built-in observability endpoints:

• GET /health - Health check with DB/Redis status
• GET /metrics - Prometheus metrics

Monitoring Guide →

Next Steps

1. Docker Deployment - Quick start with containers
2. Environment Variables - Full configuration reference
3. Troubleshooting - Common issues and solutions