Skip to content

ServerKit is a lightweight, modern server control panel for managing web applications, databases, and services on your VPS or dedicated server. Built with Python/Flask backend and React frontend.

Add comprehensive enhancement roadmap and project plan

Juan Denis0e78b56a3ac0
diff --git a/.planning/PROJECT.md b/.planning/PROJECT.md
new file mode 100644
index 00000000..aae92006
--- /dev/null
+++ b/.planning/PROJECT.md
@@ -0,0 +1,54 @@
+# ServerKit Enhancement Project
+
+## Overview
+ServerKit is a modern, self-hosted server management panel (Flask backend + React frontend) at v1.2.9. This project focuses on fixing critical infrastructure issues, adding new features, and polishing the UI for production readiness.
+
+## Current State
+- **Backend**: Flask 3.0 with 30+ services, JWT auth, WebSocket support
+- **Frontend**: React 18 with Vite, Recharts, Lucide icons, LESS styling
+- **Infrastructure**: Docker-first deployment, Nginx reverse proxy, multi-database support
+
+## Critical Issues Identified
+1. **Docker port/domain mapping not working** - Nginx proxies to `127.0.0.1:{port}` but containers may not be exposed correctly
+2. **Template icons URLs broken** - Some icon references not loading
+3. **No historical metrics** - Dashboard shows real-time only, no graphs over time
+
+## Project Goals
+
+### Priority 1: Fix Critical Infrastructure
+- Debug and fix Docker container port exposure to host
+- Fix domain-to-application routing via Nginx
+- Ensure WordPress, PHP, Flask templates deploy and route correctly
+
+### Priority 2: Add Private URL Feature
+- Generate unique private URLs for apps (e.g., `/p/abc123`)
+- Allow custom private slugs
+- Apps accessible without public indexing
+
+### Priority 3: UI/UX Polish
+- Improve Applications list and management pages
+- Fix Templates page icons and update filtering
+- Enhance FileManager disk usage visualization
+- Add historical metrics graphs to Dashboard (CPU, Memory, Disk over time)
+
+## Tech Stack
+- **Backend**: Python 3.11+, Flask, SQLAlchemy, Flask-SocketIO, psutil
+- **Frontend**: React 18, Vite, Recharts, Lucide React, LESS
+- **Infrastructure**: Docker, Nginx, Let's Encrypt
+
+## Key Files
+- Docker Service: `backend/app/services/docker_service.py`
+- Nginx Service: `backend/app/services/nginx_service.py`
+- Template Service: `backend/app/services/template_service.py`
+- Domain API: `backend/app/api/domains.py`
+- Dashboard: `frontend/src/pages/Dashboard.jsx`
+- Templates Page: `frontend/src/pages/Templates.jsx`
+- FileManager: `frontend/src/pages/FileManager.jsx`
+
+## Success Criteria
+- [ ] Docker apps accessible via connected domains
+- [ ] WordPress, PHP, Flask templates deploy and work end-to-end
+- [ ] Private URLs functional for all app types
+- [ ] Dashboard shows historical CPU/Memory/Disk graphs
+- [ ] Template icons load correctly
+- [ ] FileManager shows improved disk usage UI
diff --git a/.planning/ROADMAP.md b/.planning/ROADMAP.md
new file mode 100644
index 00000000..9e33353b
--- /dev/null
+++ b/.planning/ROADMAP.md
@@ -0,0 +1,479 @@
+# ServerKit Enhancement Roadmap
+
+> **Milestone 1**: Infrastructure Fixes, Private URLs & UI Polish
+> **Started**: 2026-01-19
+> **Status**: In Progress
+
+---
+
+## Phase Overview
+
+| Phase | Name | Status | Goal |
+|-------|------|--------|------|
+| 1 | Docker & Domain Debugging | pending | Fix port mapping and domain routing for Docker apps |
+| 2 | WordPress Template Testing | pending | Deploy and verify WordPress works end-to-end |
+| 3 | PHP App Template Testing | pending | Deploy and verify PHP/Laravel apps work correctly |
+| 4 | Flask/Python Template Testing | pending | Deploy and verify Python apps route correctly |
+| 5 | Private URL System | pending | Add private URL generation and custom slugs |
+| 6 | Dashboard Historical Metrics | pending | Add CPU/Memory/Disk graphs over time |
+| 7 | Templates Page Polish | pending | Fix icons, update URLs, improve filtering |
+| 8 | Applications UI Polish | pending | Improve app list and management pages |
+| 9 | FileManager Disk Usage UI | pending | Better visualization for disk usage |
+| 10 | Integration Testing | pending | End-to-end testing of all features |
+
+---
+
+## Phase 1: Docker & Domain Debugging
+**Goal**: Fix the critical issue where Docker apps are not accessible via connected domains
+
+### Context
+- Nginx proxies to `http://127.0.0.1:{port}` expecting Docker container exposed on localhost
+- 404 errors with retries indicate proxy can't reach container
+- No request logs in Docker app means traffic isn't reaching container
+
+### Tasks
+1. **Audit Docker port exposure logic**
+ - Review `docker_service.py` container creation
+ - Check if `-p {host_port}:{container_port}` is correctly applied
+ - Verify port binding to `0.0.0.0` vs `127.0.0.1`
+
+2. **Audit Nginx configuration generation**
+ - Review `nginx_service.py` DOCKER_SITE_TEMPLATE
+ - Verify site is created in `sites-available`
+ - Verify symlink exists in `sites-enabled`
+ - Check Nginx reload after config changes
+
+3. **Add debugging endpoints**
+ - Create `/api/v1/debug/port-check/{port}` to verify port accessibility
+ - Create `/api/v1/debug/nginx-config/{app_name}` to view generated config
+ - Add container port inspection to Docker API responses
+
+4. **Fix identified issues**
+ - Ensure containers expose ports to host correctly
+ - Ensure Nginx configs are properly enabled
+ - Add validation before domain creation
+
+5. **Add diagnostic UI**
+ - Show port binding status in Application detail
+ - Show Nginx config status (exists, enabled, valid)
+ - Add "Test Connection" button for domains
+
+### Success Criteria
+- [ ] Docker containers expose ports to localhost correctly
+- [ ] Nginx configs are created and enabled automatically
+- [ ] Domains route traffic to Docker containers
+- [ ] Diagnostic info visible in UI
+
+### Research Needed
+- [ ] How Docker Compose port mapping differs from `docker run -p`
+- [ ] Windows Docker Desktop network mode behavior
+
+---
+
+## Phase 2: WordPress Template Testing
+**Goal**: Verify WordPress template deploys and works with domain routing
+
+### Tasks
+1. **Deploy WordPress template**
+ - Use existing WordPress template from marketplace
+ - Configure with test domain
+ - Document any errors encountered
+
+2. **Verify database connectivity**
+ - Ensure MySQL container is accessible
+ - Verify WordPress can connect to database
+ - Check environment variables passed correctly
+
+3. **Test domain access**
+ - Verify Nginx config generated correctly
+ - Test HTTP access via domain
+ - Verify WordPress installation wizard loads
+
+4. **Document issues and fixes**
+ - Log all errors encountered
+ - Apply fixes from Phase 1 if needed
+ - Update template if issues are template-specific
+
+### Success Criteria
+- [ ] WordPress container starts successfully
+- [ ] Database connection works
+- [ ] Domain routes to WordPress
+- [ ] Installation wizard accessible
+
+---
+
+## Phase 3: PHP App Template Testing
+**Goal**: Verify PHP/Laravel apps deploy and route correctly
+
+### Tasks
+1. **Test PHP-FPM template deployment**
+ - Deploy a basic PHP app
+ - Verify PHP-FPM socket connection
+ - Test Nginx fastcgi_pass configuration
+
+2. **Test Laravel template if available**
+ - Deploy Laravel template
+ - Verify artisan commands work
+ - Test database migrations
+
+3. **Verify static asset serving**
+ - Check CSS/JS files load correctly
+ - Verify public directory routing
+
+4. **Document PHP-specific issues**
+ - PHP version compatibility
+ - Extension requirements
+ - Permission issues
+
+### Success Criteria
+- [ ] PHP apps execute correctly via Nginx
+- [ ] Static assets served properly
+- [ ] Laravel-specific features work (if applicable)
+
+---
+
+## Phase 4: Flask/Python Template Testing
+**Goal**: Verify Python apps deploy and route correctly
+
+### Tasks
+1. **Test Flask template deployment**
+ - Deploy Flask template
+ - Verify Gunicorn starts correctly
+ - Check port binding
+
+2. **Test reverse proxy to Gunicorn**
+ - Verify Nginx proxy_pass works
+ - Test WebSocket upgrades if applicable
+ - Check static file serving via Nginx
+
+3. **Test Django template if available**
+ - Deploy Django template
+ - Verify collectstatic works
+ - Test admin interface access
+
+4. **Document Python-specific issues**
+ - Virtual environment setup
+ - Dependency installation
+ - WSGI/ASGI configuration
+
+### Success Criteria
+- [ ] Python apps run via Gunicorn/uWSGI
+- [ ] Nginx proxies requests correctly
+- [ ] Static files served properly
+
+---
+
+## Phase 5: Private URL System
+**Goal**: Allow apps to have private, non-indexed URLs for sharing
+
+### Backend Tasks
+1. **Database schema updates**
+ - Add `private_slug` field to Application model (unique, nullable)
+ - Add `is_private` boolean field
+ - Add `private_url_enabled` boolean field
+ - Create migration
+
+2. **Private URL generation service**
+ - Create `PrivateURLService` in `backend/app/services/`
+ - Generate cryptographically secure slugs (e.g., `nanoid` style)
+ - Allow custom slug validation (alphanumeric, hyphens, 3-50 chars)
+ - Prevent slug collisions
+
+3. **API endpoints**
+ - `POST /api/v1/apps/{id}/private-url` - Enable/generate private URL
+ - `PUT /api/v1/apps/{id}/private-url` - Update custom slug
+ - `DELETE /api/v1/apps/{id}/private-url` - Disable private URL
+ - `GET /api/v1/p/{slug}` - Resolve private URL to app (public endpoint)
+
+4. **Nginx integration**
+ - Generate Nginx config for private URL route
+ - Route `/p/{slug}` to correct container port
+ - Handle both private URL and domain access
+
+### Frontend Tasks
+5. **Application settings UI**
+ - Add "Private URL" section in Application detail
+ - Toggle to enable/disable
+ - Input for custom slug with validation
+ - Copy button for private URL
+ - Show generated URL preview
+
+6. **Applications list update**
+ - Show private URL indicator icon
+ - Quick copy action for private URL
+
+### Success Criteria
+- [ ] Private URLs can be generated for any app
+- [ ] Custom slugs work with validation
+- [ ] Private URL routes to correct container
+- [ ] UI allows easy management and copying
+
+---
+
+## Phase 6: Dashboard Historical Metrics
+**Goal**: Add time-series graphs for CPU, Memory, and Disk usage
+
+### Backend Tasks
+1. **Metrics storage system**
+ - Create `MetricsHistory` model or use time-series file storage
+ - Store metrics every 60 seconds (configurable)
+ - Retain 24 hours of minute-level data
+ - Retain 7 days of hourly aggregates
+ - Retain 30 days of daily aggregates
+
+2. **Metrics collection service**
+ - Create background task to collect and store metrics
+ - Use existing `psutil` calls from monitoring service
+ - Add data aggregation for older data points
+
+3. **Historical metrics API**
+ - `GET /api/v1/metrics/history?period=1h|6h|24h|7d|30d`
+ - Return time-series data for CPU, Memory, Disk
+ - Include min, max, avg for each time bucket
+
+### Frontend Tasks
+4. **Dashboard graph components**
+ - Create `MetricsGraph` component using Recharts
+ - Support multiple metrics on one graph
+ - Add time period selector (1h, 6h, 24h, 7d, 30d)
+ - Show current value + trend indicator
+
+5. **CPU usage graph**
+ - Line chart showing CPU % over time
+ - Color coding for high usage periods
+ - Hover tooltip with exact values
+
+6. **Memory usage graph**
+ - Area chart showing used/total memory
+ - Show both percentage and absolute values
+ - Include swap usage if available
+
+7. **Disk usage graph**
+ - Area chart showing used/total disk
+ - Per-mount breakdown if multiple disks
+ - Growth rate indicator
+
+8. **Dashboard layout update**
+ - Reorganize dashboard to fit graphs
+ - Keep real-time stats in header cards
+ - Add graphs below current stats section
+
+### Success Criteria
+- [ ] Metrics stored persistently
+- [ ] Historical data queryable by time period
+- [ ] Graphs display correctly with interactions
+- [ ] Dashboard remains performant
+
+### Research Needed
+- [ ] Best storage approach (SQLite, InfluxDB, JSON files)
+- [ ] Recharts performance with large datasets
+
+---
+
+## Phase 7: Templates Page Polish
+**Goal**: Fix broken icons, update URLs, improve filtering
+
+### Tasks
+1. **Audit current icon system**
+ - Identify broken icon URLs
+ - Check icon loading in browser dev tools
+ - Document which icons are missing
+
+2. **Fix icon URLs**
+ - Update template `index.json` with correct icon URLs
+ - Use reliable CDN or local icons
+ - Add fallback icon for missing images
+
+3. **Improve category filtering**
+ - Add clear filter chips showing active filters
+ - Add "Clear all filters" button
+ - Remember filter state in URL params
+ - Add search by template name
+
+4. **Update template cards**
+ - Show version number
+ - Show last updated date
+ - Add "Popular" or "Featured" badges
+ - Improve install button visibility
+
+5. **Add template details modal**
+ - Show full description
+ - List required variables
+ - Show Docker Compose preview
+ - Display system requirements
+
+### Success Criteria
+- [ ] All icons load correctly
+- [ ] Filtering is intuitive and persistent
+- [ ] Template cards show useful info
+- [ ] Details modal provides complete info
+
+---
+
+## Phase 8: Applications UI Polish
+**Goal**: Improve the applications list and management pages
+
+### Tasks
+1. **Applications list improvements**
+ - Add status indicators (running, stopped, error)
+ - Show port and domain info inline
+ - Add quick actions (start, stop, restart)
+ - Improve grid/list view toggle
+ - Add sorting options (name, status, created, updated)
+
+2. **Application detail page**
+ - Reorganize into clear sections/tabs
+ - Add real-time logs preview
+ - Show resource usage (CPU, Memory per container)
+ - Improve environment variables UI
+ - Add deployment history section
+
+3. **Manage app page improvements**
+ - Clearer action buttons with icons
+ - Confirmation dialogs for destructive actions
+ - Status messages for async operations
+ - Better error display
+
+4. **Add bulk actions**
+ - Select multiple apps
+ - Bulk start/stop/restart
+ - Bulk delete with confirmation
+
+### Success Criteria
+- [ ] App status visible at a glance
+- [ ] Quick actions work reliably
+- [ ] Detail page is well-organized
+- [ ] Bulk actions functional
+
+---
+
+## Phase 9: FileManager Disk Usage UI
+**Goal**: Improve disk usage visualization in FileManager
+
+### Tasks
+1. **Enhanced disk usage widget**
+ - Visual progress bar for each mount point
+ - Color coding (green < 70%, yellow < 90%, red >= 90%)
+ - Show used/total/free space
+ - Percentage and absolute values
+
+2. **Directory size analysis**
+ - Add "Analyze" button for current directory
+ - Show size of subdirectories
+ - Treemap or bar chart visualization
+ - Identify largest files/folders
+
+3. **Storage breakdown**
+ - Pie chart showing space by file type
+ - List largest files in current directory
+ - Show hidden files space usage
+
+4. **UI improvements**
+ - Move disk usage to collapsible sidebar panel
+ - Add refresh button for disk stats
+ - Show last updated timestamp
+ - Responsive layout for all screen sizes
+
+### Success Criteria
+- [ ] Disk usage clearly visible
+- [ ] Directory analysis functional
+- [ ] Visualization helps identify space usage
+- [ ] Responsive on all devices
+
+---
+
+## Phase 10: Integration Testing
+**Goal**: End-to-end testing of all new features
+
+### Tasks
+1. **Create test plan document**
+ - List all features to test
+ - Define test scenarios
+ - Document expected results
+
+2. **Docker & Domain tests**
+ - Deploy each template type
+ - Verify domain routing
+ - Test SSL certificate provisioning
+ - Test multiple domains per app
+
+3. **Private URL tests**
+ - Generate private URLs
+ - Test custom slugs
+ - Verify access control
+ - Test with different app types
+
+4. **Dashboard tests**
+ - Verify metrics collection
+ - Test all time periods
+ - Check graph accuracy
+ - Test real-time updates
+
+5. **UI tests**
+ - Test all template filters
+ - Verify icon loading
+ - Test app management flows
+ - Verify FileManager features
+
+6. **Performance testing**
+ - Check dashboard load time
+ - Test with many apps
+ - Verify WebSocket stability
+ - Check memory usage
+
+7. **Document findings**
+ - Create bug reports for issues found
+ - Document workarounds
+ - Update user documentation
+
+### Success Criteria
+- [ ] All features pass testing
+- [ ] No critical bugs remain
+- [ ] Performance is acceptable
+- [ ] Documentation updated
+
+---
+
+## Dependencies
+
+```
+Phase 1 (Docker/Domain) ─┬─► Phase 2 (WordPress)
+ ├─► Phase 3 (PHP)
+ ├─► Phase 4 (Flask)
+ └─► Phase 5 (Private URLs)
+
+Phase 5 (Private URLs) ──► Phase 8 (Apps UI) ──► Phase 10 (Testing)
+
+Phase 6 (Metrics) ───────► Phase 10 (Testing)
+
+Phase 7 (Templates) ─────► Phase 10 (Testing)
+
+Phase 9 (FileManager) ───► Phase 10 (Testing)
+```
+
+---
+
+## Notes
+
+- **Phase 1 is critical** - must be completed before testing any templates
+- Phases 2-4 can run in parallel after Phase 1
+- Phases 6, 7, 8, 9 are independent and can be worked in any order
+- Phase 10 should run last after all features are implemented
+- Consider creating feature branches for each phase
+
+---
+
+## Estimated Complexity
+
+| Phase | Complexity | Files Changed |
+|-------|------------|---------------|
+| 1 | High | 5-8 |
+| 2 | Medium | 1-2 (mostly testing) |
+| 3 | Medium | 1-2 (mostly testing) |
+| 4 | Medium | 1-2 (mostly testing) |
+| 5 | High | 8-12 |
+| 6 | High | 6-10 |
+| 7 | Medium | 3-5 |
+| 8 | Medium | 4-6 |
+| 9 | Medium | 2-4 |
+| 10 | Low | 0 (testing only) |
diff --git a/.planning/STATE.md b/.planning/STATE.md
new file mode 100644
index 00000000..563b9671
--- /dev/null
+++ b/.planning/STATE.md
@@ -0,0 +1,34 @@
+# ServerKit Enhancement - State
+
+## Current Status
+- **Milestone**: 1 - Infrastructure Fixes, Private URLs & UI Polish
+- **Current Phase**: 1 - Docker & Domain Debugging
+- **Phase Status**: Not Started
+- **Last Updated**: 2026-01-19
+
+## Phase Progress
+
+| Phase | Status | Started | Completed |
+|-------|--------|---------|-----------|
+| 1 | pending | - | - |
+| 2 | pending | - | - |
+| 3 | pending | - | - |
+| 4 | pending | - | - |
+| 5 | pending | - | - |
+| 6 | pending | - | - |
+| 7 | pending | - | - |
+| 8 | pending | - | - |
+| 9 | pending | - | - |
+| 10 | pending | - | - |
+
+## Blockers
+None currently identified.
+
+## Notes
+- Phase 1 is critical path - all template testing depends on it
+- User reported 404 errors when accessing Docker app domains
+- No request logs visible in Docker containers
+
+## Quick Links
+- [ROADMAP.md](./ROADMAP.md)
+- [PROJECT.md](./PROJECT.md)
diff --git a/.planning/STRATEGIC_ROADMAP.md b/.planning/STRATEGIC_ROADMAP.md
deleted file mode 100644
index 2decd85b..00000000
--- a/.planning/STRATEGIC_ROADMAP.md
+++ /dev/null
@@ -1,424 +0,0 @@
-# ServerKit Strategic Roadmap
-
-*Last Updated: January 2026*
-
-This roadmap outlines the strategic development path for ServerKit to achieve competitive parity and differentiation in the self-hosted server management market.
-
----
-
-## Vision Statement
-
-**ServerKit: The modern server panel that bridges traditional hosting and cloud-native deployment.**
-
-ServerKit will be the go-to choice for developers and small teams who want:
-- The simplicity of traditional hosting panels (like cPanel)
-- The power of modern PaaS platforms (like Coolify/Heroku)
-- Without the complexity of Kubernetes
-- Without vendor lock-in
-
----
-
-## Current State Assessment
-
-### What We Have (January 2026)
-
-| Category | Features |
-|----------|----------|
-| **Authentication** | JWT auth, role-based access, account lockout |
-| **Applications** | PHP, WordPress, Flask, Django, Docker support |
-| **Infrastructure** | Nginx config, SSL/Let's Encrypt, firewall (ufw/firewalld) |
-| **Monitoring** | Real-time metrics, uptime tracking, alerts |
-| **Operations** | File manager, web terminal, cron jobs, FTP |
-| **UI** | Modern React dashboard with dark theme |
-
-### What's Missing for Competitive Parity
-1. Git-based deployment
-2. One-click app marketplace
-3. Two-factor authentication
-4. S3 backup integration
-5. Multi-server support
-
----
-
-## Phased Roadmap
-
-## Phase 1: Security & Developer Essentials
-**Timeline: Q1 2026 (Jan-Mar)**
-**Theme: "Trust & Productivity"**
-
-### 1.1 Two-Factor Authentication [P0]
-- [ ] TOTP implementation (Google Authenticator compatible)
-- [ ] QR code setup flow
-- [ ] Backup codes generation
-- [ ] Recovery flow for lost 2FA
-- [ ] Admin enforcement option
-
-**Deliverable:** Users can secure accounts with 2FA
-
-### 1.2 Environment Variable Management [P1]
-- [ ] Per-application .env storage
-- [ ] Secret masking in UI (show/hide toggle)
-- [ ] Import from .env file
-- [ ] Export to .env file
-- [ ] Variable history/versioning
-- [ ] Encrypted storage in database
-
-**Deliverable:** Developers can manage app config without SSH
-
-### 1.3 Database Web Interface [P1]
-- [ ] Embed Adminer (single PHP file, lightweight)
-- [ ] Single sign-on from ServerKit dashboard
-- [ ] Support MySQL, PostgreSQL, SQLite
-- [ ] Alternative: custom query runner for simple tasks
-
-**Deliverable:** Database management without external tools
-
-### 1.4 Notification System [P1]
-- [ ] Discord webhook integration
-- [ ] Slack webhook integration
-- [ ] Telegram bot notifications
-- [ ] Email improvements (templates, reliability)
-- [ ] Notification preferences per user
-- [ ] Test notification button
-
-**Deliverable:** Get alerted on your preferred channel
-
----
-
-## Phase 2: Git Deployment Pipeline
-**Timeline: Q2 2026 (Apr-Jun)**
-**Theme: "Push to Deploy"**
-
-### 2.1 Git Repository Integration [P0]
-- [ ] GitHub OAuth app connection
-- [ ] GitLab integration
-- [ ] Bitbucket integration
-- [ ] Generic Git URL support (any repo)
-- [ ] Repository browser in UI
-- [ ] Branch selection
-
-**Deliverable:** Connect any Git repository
-
-### 2.2 Webhook Deployment [P0]
-- [ ] Auto-generated webhook URLs per app
-- [ ] Signature verification (GitHub, GitLab)
-- [ ] Branch-specific triggers
-- [ ] Deploy on push to `main`
-- [ ] Webhook logs and debugging
-
-**Deliverable:** Auto-deploy when you push code
-
-### 2.3 Build System [P0]
-- [ ] Dockerfile detection and building
-- [ ] Nixpacks support (Heroku-style detection)
-- [ ] Custom build commands
-- [ ] Build log streaming (WebSocket)
-- [ ] Build caching for speed
-- [ ] Build timeout handling
-
-**Deliverable:** Build and deploy any language/framework
-
-### 2.4 Deployment Management [P1]
-- [ ] Deployment history per app
-- [ ] Deployment status (building, deploying, live, failed)
-- [ ] One-click rollback to previous version
-- [ ] Keep last N deployments (configurable)
-- [ ] Deployment diff view
-
-**Deliverable:** Safe deployments with easy rollback
-
----
-
-## Phase 3: One-Click App Marketplace
-**Timeline: Q3 2026 (Jul-Sep)**
-**Theme: "Deploy Anything in Seconds"**
-
-### 3.1 Template System [P0]
-- [ ] App template schema (YAML-based)
-- [ ] Docker Compose compatibility
-- [ ] Variable substitution (ports, passwords, etc.)
-- [ ] Post-install scripts
-- [ ] Update mechanism for apps
-
-**Template schema example:**
-```yaml
-name: uptime-kuma
-version: "1.21"
-description: Self-hosted monitoring tool
-icon: /icons/uptime-kuma.png
-categories: [monitoring, devops]
-compose:
- services:
- uptime-kuma:
- image: louislam/uptime-kuma:1
- ports:
- - "${PORT}:3001"
- volumes:
- - data:/app/data
-variables:
- PORT:
- default: 3001
- description: "Port to expose"
-```
-
-### 3.2 Initial App Catalog (50 Apps) [P0]
-
-**Development & DevOps:**
-- [ ] Gitea / GitLab
-- [ ] Drone CI / Woodpecker CI
-- [ ] SonarQube
-- [ ] Vault (secrets)
-- [ ] Uptime Kuma
-
-**Databases:**
-- [ ] PostgreSQL
-- [ ] MySQL / MariaDB
-- [ ] MongoDB
-- [ ] Redis
-- [ ] InfluxDB
-
-**CMS & Content:**
-- [ ] WordPress
-- [ ] Ghost
-- [ ] Strapi
-- [ ] Directus
-- [ ] Payload CMS
-
-**Productivity:**
-- [ ] Nextcloud
-- [ ] Minio (S3)
-- [ ] Vaultwarden (passwords)
-- [ ] n8n (automation)
-- [ ] Appwrite
-
-**Communication:**
-- [ ] Mattermost
-- [ ] Rocket.Chat
-- [ ] Mailcow (email)
-- [ ] Listmonk (newsletters)
-
-**Analytics & Monitoring:**
-- [ ] Plausible Analytics
-- [ ] Umami
-- [ ] Grafana
-- [ ] Prometheus
-
-### 3.3 App Marketplace UI [P1]
-- [ ] Browse by category
-- [ ] Search functionality
-- [ ] App detail pages with screenshots
-- [ ] One-click deploy button
-- [ ] Configuration wizard
-- [ ] Installed apps management
-
-**Deliverable:** 50+ apps deployable in one click
-
----
-
-## Phase 4: Backup & Recovery
-**Timeline: Q4 2026 (Oct-Dec)**
-**Theme: "Never Lose Data"**
-
-### 4.1 S3-Compatible Backup [P0]
-- [ ] AWS S3 support
-- [ ] MinIO support (self-hosted)
-- [ ] Backblaze B2 support
-- [ ] DigitalOcean Spaces
-- [ ] Any S3-compatible endpoint
-
-### 4.2 Backup Features [P0]
-- [ ] Scheduled backups (cron-based)
-- [ ] On-demand backups
-- [ ] Backup encryption (AES-256)
-- [ ] Compression (gzip/zstd)
-- [ ] Backup verification
-- [ ] Retention policies (keep last N)
-
-### 4.3 Restore Capabilities [P1]
-- [ ] One-click restore from backup
-- [ ] Selective restore (files/database)
-- [ ] Point-in-time recovery
-- [ ] Download backup locally
-- [ ] Restore to different server
-
-### 4.4 What Gets Backed Up
-- [ ] Application files
-- [ ] Database dumps
-- [ ] SSL certificates
-- [ ] Nginx configurations
-- [ ] Environment variables
-- [ ] Cron jobs
-
-**Deliverable:** Complete disaster recovery solution
-
----
-
-## Phase 5: Multi-Server Architecture
-**Timeline: Q1 2027**
-**Theme: "Scale Without Limits"**
-
-### 5.1 Server Agent [P0]
-- [ ] Standalone agent binary (Python/Go)
-- [ ] Authenticated connection to control panel
-- [ ] Auto-registration flow
-- [ ] Health reporting
-- [ ] Secure communication (TLS + JWT)
-
-### 5.2 Multi-Server Management [P0]
-- [ ] Add/remove servers from dashboard
-- [ ] Server grouping and tagging
-- [ ] Per-server resource monitoring
-- [ ] Server status overview
-
-### 5.3 Cross-Server Features [P1]
-- [ ] Deploy app to any connected server
-- [ ] Centralized logging
-- [ ] Aggregated metrics dashboard
-- [ ] Server-to-server migration
-
-**Deliverable:** Manage entire infrastructure from one panel
-
----
-
-## Phase 6: Team & Enterprise Features
-**Timeline: Q2 2027**
-**Theme: "Collaborate Securely"**
-
-### 6.1 Team Management [P1]
-- [ ] Create organizations
-- [ ] Invite team members
-- [ ] Role-based access (Admin, Developer, Viewer)
-- [ ] Per-app permissions
-- [ ] Audit logging
-
-### 6.2 Advanced Security [P1]
-- [ ] SSO/SAML integration
-- [ ] LDAP/Active Directory
-- [ ] IP whitelist for dashboard
-- [ ] Session management
-- [ ] Security event alerts
-
-### 6.3 Developer Experience [P2]
-- [ ] CLI tool (`serverkit` command)
-- [ ] API tokens for CI/CD
-- [ ] Terraform provider
-- [ ] Public API documentation
-
-**Deliverable:** Enterprise-ready team features
-
----
-
-## Phase 7: Advanced Features
-**Timeline: Q3-Q4 2027**
-**Theme: "Power User Tools"**
-
-### 7.1 Staging & Previews
-- [ ] Create staging environments
-- [ ] PR preview deployments
-- [ ] Environment promotion workflow
-- [ ] Isolated staging databases
-
-### 7.2 Advanced Monitoring
-- [ ] Custom metrics collection
-- [ ] Log search and filtering
-- [ ] Performance profiling
-- [ ] Error tracking integration (Sentry)
-
-### 7.3 Networking
-- [ ] Internal networking between apps
-- [ ] Load balancer configuration
-- [ ] TCP/UDP proxy support
-- [ ] WebSocket support improvements
-
----
-
-## Milestone Summary
-
-| Version | Milestone | Target | Key Features |
-|---------|-----------|--------|--------------|
-| **v0.5** | Security Ready | Mar 2026 | 2FA, env vars, notifications |
-| **v0.6** | Git Deploy | Jun 2026 | Push-to-deploy, rollback |
-| **v0.7** | App Store | Sep 2026 | 50+ one-click apps |
-| **v0.8** | Backup Pro | Dec 2026 | S3 backups, restore |
-| **v0.9** | Multi-Server | Mar 2027 | Server agents, fleet management |
-| **v1.0** | Production Ready | Jun 2027 | Teams, enterprise features |
-
----
-
-## Success Metrics
-
-### User Adoption
-- 1,000 GitHub stars by v1.0
-- 500 active installations
-- 10+ community contributors
-
-### Feature Parity
-- Match Coolify core features by v0.8
-- Exceed CloudPanel features by v0.6
-- Complete WordPress toolkit by v0.7
-
-### Performance
-- Dashboard load < 1 second
-- Deploy completion < 2 minutes
-- Support 100 apps per server
-
-### Reliability
-- 99.9% panel uptime
-- Zero data loss in backups
-- Automated disaster recovery
-
----
-
-## Competitive Positioning by Version
-
-| Version | vs Coolify | vs CloudPanel | vs HestiaCP |
-|---------|------------|---------------|-------------|
-| v0.5 | -80% | -20% | +10% |
-| v0.6 | -50% | +30% | +40% |
-| v0.7 | -20% | +60% | +60% |
-| v0.8 | Match | +70% | +70% |
-| v1.0 | +10% | +100% | +80% |
-
-*Percentage represents feature coverage comparison*
-
----
-
-## Resource Allocation
-
-### Recommended Team
-- 1-2 Backend developers (Flask, system integration)
-- 1 Frontend developer (React)
-- 0.5 DevOps (testing, CI/CD)
-- Community contributors
-
-### Technical Priorities
-1. Backend stability and security
-2. API completeness
-3. Frontend polish
-4. Documentation
-5. Testing coverage
-
----
-
-## Risk Mitigation
-
-| Risk | Mitigation |
-|------|------------|
-| Scope creep | Strict phase boundaries, MVP first |
-| Security vulnerabilities | Security audit before v1.0 |
-| Performance at scale | Load testing each phase |
-| Community adoption | Open roadmap, contributor docs |
-| Maintenance burden | Automated testing, CI/CD |
-
----
-
-## Next Steps
-
-1. **This Week:** Begin 2FA implementation
-2. **This Month:** Complete Phase 1.1 and 1.2
-3. **This Quarter:** Ship v0.5 with all Phase 1 features
-4. **Review:** Quarterly roadmap review and adjustment
-
----
-
-*This roadmap is a living document. Review and update quarterly based on user feedback and market changes.*