The Playwright browser download (Chrome for Testing + Chrome Headless Shell + FFmpeg, ~170MB total) is the single largest cost in the start-app composite action. Observed in a recent E2E run: 4m15s to download cold vs ~10s on a warm cache. Across weekly cache evictions and the ~30% of runs that hit a cold cache, that is multiple action minutes per PR averaged over time, and several minutes of wall-time regression on any individual cold run. Split the existing `playwright install --with-deps chromium` step into two halves: 1. `playwright install-deps chromium` runs unconditionally because apt packages live under /var and are not preserved by actions/cache. This is fast (~10s). 2. `playwright install chromium` runs only when the browser cache under ~/.cache/ms-playwright misses. The cache key is pinned to the @playwright/test version read from the root package.json, so a future bump invalidates the cache automatically and the old browsers are replaced cleanly. Sharding (the other half of the original optimization plan) was evaluated and rejected. With ~80s of per-job setup and only ~60s of test time, 2-way sharding would roughly double action minutes while saving only ~5s of wall time on warm runs. The math only pencils out when test time significantly exceeds setup time, which is not the case for Sencho today. Revisit if the suite grows past ~5 minutes of pure test time.
Sencho
A self-hosted Docker Compose management dashboard. Manage your stacks, containers, images, volumes, and networks through a modern web UI.
Features
- Stack Management - Create, edit, start, stop, and remove Docker Compose stacks with a built-in Monaco code editor
- Multi-Node Support - Manage remote Sencho instances through a transparent HTTP/WebSocket proxy (Distributed API model)
- App Store - One-click deployment from LinuxServer.io templates with editable ports, volumes, and environment variables
- Resource Hub - Browse and manage images, volumes, and networks with managed/external/unused classification
- Live Logs - Aggregated real-time log streaming across all containers with search and filtering
- Dashboard - Container stats, CPU/RAM metrics, health checks, and image update notifications
- Alerts - Configurable threshold alerts for CPU, RAM, and disk usage
- Terminal - In-browser host console and container exec via WebSocket
Quick Start
services:
sencho:
image: saelix/sencho:latest
container_name: sencho
restart: unless-stopped
ports:
- "3000:3000"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ./data:/app/data
# 1:1 Compose Path Rule: host path MUST match container path
- /opt/docker:/opt/docker
environment:
- COMPOSE_DIR=/opt/docker
- DATA_DIR=/app/data
docker compose up -d
Then open http://your-server:3000 and create your admin account.
See the full documentation for configuration details, multi-node setup, and more.
Development
# Backend (Express + TypeScript)
cd backend && npm install && npm run dev
# Frontend (React + Vite)
cd frontend && npm install && npm run dev
The frontend dev server proxies /api requests to the backend on port 3000.
Contributing
See CONTRIBUTING.md for development setup and PR guidelines.
Security
See SECURITY.md for vulnerability reporting. Do not open public issues for security vulnerabilities.
License
Sencho is licensed under the Business Source License 1.1. You may use, modify, and redistribute the code freely, including for production use. The only restriction is offering Sencho as a competing hosted or managed service. On 2030-03-25, the license automatically converts to Apache 2.0.
