Files
ServerKit/docs
Juan DenisandClaude Opus 4.8 6ef998515d feat(wordpress): per-site uptime + auto-incidents (#26)
Make a managed WordPress site appear on a status page with a real uptime %
and auto-incidents, driven by an autonomous server-side health poller.

Scheduler: a single-worker-guarded daemon thread (_start_health_check_
scheduler, 300s) runs EnvironmentHealthService.check_health for every RUNNING
production site (skips archived/stopped so an intentional stop is not an
outage). This keeps health_status fresh autonomously — so #27's transition
alerts fire without the browser health card open — and drives bound
status-page components. HealthCheck samples are pruned to 90 days (once/day)
to bound growth.

Schema (Alembic 010 + the boot-time _fix_missing_columns auto-add):
- status_components.wordpress_site_id  (-> wordpress_sites)
- status_incidents.component_id        (-> status_components)
The existing HealthCheck table is reused as the uptime sample store.

StatusPageService.sync_component_from_health maps the health verdict
(healthy->operational, degraded->degraded, unhealthy->major_outage; unknown
skipped), records a HealthCheck, recomputes a real COUNT-based uptime %
(24h/7d/30d/90d; only fully-healthy checks count), and auto-opens an incident
on ENTERING a major outage / auto-resolves on LEAVING it (operational OR
degraded, so a degraded intermediate never strands the incident).

Routes GET/POST/DELETE /sites/<id>/status-page read the binding + attach
(production-only) / detach (resolves & unlinks the incident first -> no
dangling FK on PostgreSQL, no stale public incident). New Uptime tab on the
site detail (health + uptime % + attach/detach).

Security: internal probe config (check_target, intervals) is stripped from the
unauthenticated public-page projection, and a health-driven component stores
no internal localhost:port target.

Review fixes (3-lens adversarial pass): incident-resolve edge for the
degraded-recovery path; detach FK/orphan cleanup in delete_component; public
check_target leak; production-only attach; uptime-prune; degraded-uptime
semantics documented. Verified: backend py_compile, frontend lint + build.
Not runtime-exercised on a real Docker host (Windows dev).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-01 00:47:26 -04:00
..

ServerKit Documentation

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


Document Description
Installation Guide Complete setup instructions for Docker and manual installation
Architecture System design, request flow, and diagrams
Deployment Guide Production deployment, CLI commands, and configuration
Local Development Run the panel locally for development
API Reference REST API documentation with examples
Multi-Environment Guide Set up prod/dev WordPress pairs with shared database
Multi-Server & Agent Install the agent and connect remote servers (see also pairing)

Getting Started

1. Installation

Choose your preferred installation method:

2. Initial Setup

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

3. Start Managing

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

Feature Guides

Application Management

ServerKit supports multiple application types:

Type Runtime Process Manager
PHP / WordPress PHP-FPM 8.x Nginx
Python (Flask/Django) Python 3.x Gunicorn
Node.js Node 18+ PM2
Docker Containers Docker Engine

Each application includes:

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

Multi-Environment Support

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.

Domain & SSL

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

Database Management

Supported databases:

  • MySQL / MariaDB
  • PostgreSQL

Features:

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

Monitoring & Alerts

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

Security

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

Scheduled Tasks

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

Configuration

Environment Variables

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

Notification Setup

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

CLI Reference

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.


API Reference

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 complete documentation.


Troubleshooting

Common Issues

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.


Additional Resources


Support

  • 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