Welcome to the ServerKit documentation. This guide will help you install, configure, and use ServerKit effectively.

Choose your preferred installation method:

• Docker Installation (Recommended) - Get started in minutes
• Manual Installation - Full control over the setup
• One-Line Install - One-line installer for Ubuntu, Debian, Fedora, and RHEL/Rocky/AlmaLinux

After installation:

1. Access ServerKit at http://your-server-ip
2. Create your admin account (first user becomes admin)
3. Enable Two-Factor Authentication
4. Configure Notifications

• Add your first application from the Applications page
• Configure domains and SSL certificates
• Set up monitoring alerts
• Enable security scanning

ServerKit supports multiple application types:

Each application includes:

• Environment variable management (encrypted)
• Log viewing and streaming
• Start/stop/restart controls
• Domain and SSL configuration

ServerKit supports multi-environment linking for WordPress and other applications:

• Production/Development Pairs - Link apps as prod/dev environments
• Shared Database - Both environments can share the same MySQL database with different table prefixes
• Environment Badges - Visual indicators (PROD/DEV/STAGING) in the UI
• Quick Navigation - One-click switching between linked environments
• Credential Propagation - Automatically share database credentials between linked apps

Common use case: WordPress theme development

1. Production WordPress serves live traffic
2. Development WordPress shares the database (separate tables)
3. Develop themes in dev without affecting production

See the Multi-Environment Setup Guide for detailed instructions.

• Nginx Virtual Hosts - Automatic configuration generation
• Let's Encrypt SSL - Free certificates with auto-renewal
• Custom Certificates - Upload your own SSL certificates

Supported databases:

• MySQL / MariaDB
• PostgreSQL

Features:

• Create/delete databases
• User management
• Basic query interface

Real-time monitoring includes:

• CPU, RAM, disk usage
• Network traffic
• Server uptime history
• Process monitoring

Alert channels:

• Discord webhooks
• Slack webhooks
• Telegram bot
• Generic HTTP webhooks

• Two-Factor Authentication - TOTP-based (Google Authenticator, Authy)
• Malware Scanning - ClamAV integration
• File Integrity Monitoring - Detect unauthorized changes
• Firewall Management - UFW rule configuration

• Visual cron job editor
• Execution history
• Enable/disable jobs
• Common schedule presets

ServerKit is configured via environment variables. See .env.example for all options.

Required variables:

SECRET_KEY=your-secret-key
JWT_SECRET_KEY=your-jwt-secret

Database options:

# SQLite (default)
DATABASE_URL=sqlite:///serverkit.db

# PostgreSQL (production)
DATABASE_URL=postgresql://user:pass@localhost/serverkit

Configure webhooks in Settings > Notifications or via environment:

DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/...
SLACK_WEBHOOK_URL=https://hooks.slack.com/services/...
TELEGRAM_BOT_TOKEN=your-bot-token
TELEGRAM_CHAT_ID=your-chat-id

ServerKit includes a management CLI:

# Service Management
serverkit start|stop|restart|status
serverkit logs [backend|frontend]
serverkit update

# User Management
serverkit create-admin
serverkit reset-password
serverkit list-users

# Database
serverkit init-db
serverkit migrate-db          # Apply schema updates
serverkit backup-db
serverkit restore-db <file>

# App Management
serverkit list-apps           # List all installed apps

# Cleanup Commands
serverkit cleanup-apps        # Delete all apps and containers
serverkit cleanup-apps --delete-volumes   # Also delete Docker volumes
serverkit factory-reset       # Complete reset (delete everything)

# Utilities
serverkit generate-keys
serverkit config

See Deployment Guide for complete CLI documentation.

ServerKit provides a REST API for automation and integration.

Base URL: http://localhost:47927/api/v1

Authentication: JWT Bearer tokens

Quick example:

# Login
curl -X POST http://localhost:47927/api/v1/auth/login \
  -H "Content-Type: application/json" \
  -d '{"username": "admin", "password": "password"}'

# Use token
curl http://localhost:47927/api/v1/system/stats \
  -H "Authorization: Bearer <token>"

See API Reference for curated examples.

Auto-generated API docs: the running panel generates an OpenAPI 3.0 spec from the actual routes and serves Swagger UI at /api/v1/docs (raw spec at /api/v1/docs/openapi.json). That is always in sync with the code — prefer it over API.md when the two disagree.

The docs/ folder mixes three audiences. Use this map to find what you need:

User / operator docs (stable, safe to rely on): Installation · Deployment · Local Development · Architecture · Backup & Protection · Multi-Environment · Agent Pairing · MCP Server Access · Cloudflare Token Scopes · Coexistence · Runbooks

Extension & platform author docs: Extensions · Extensions CI · Extensions Registry · Registries · serverkit.yaml · Template Catalog Schema · Theming · Fleet Contract · Workspace Scoping · Notifications Contract · ADRs

Internal working docs (dev plans, specs, audits — may be stale or aspirational, not user documentation): plans/ · audits/ · roadmap and spec files at this level (*_ROADMAP.md, *_SPEC.md, ENHANCEMENTS.md, NEW_FEATURES.md, etc.)

Container won't start:

docker compose logs backend
sudo lsof -i :47927

502 Bad Gateway:

sudo systemctl status serverkit
sudo tail -f /var/log/serverkit/error.log

ClamAV not working:

sudo freshclam
sudo systemctl restart clamav-daemon

See Installation Guide - Troubleshooting for more solutions.

• Main README - Project overview and quick start
• Roadmap - Development plans and upcoming features
• Contributing Guide - How to contribute
• GitHub Issues - Report bugs or request features

• Bug Reports: GitHub Issues
• Feature Requests: GitHub Issues with enhancement label
• Security Issues: Please report privately via GitHub Security Advisories

ServerKit Documentation
Version 1.6.7