mirror of
https://github.com/Studio-Saelix/sencho.git
synced 2026-07-26 11:49:16 +00:00
Anso
32a7d53b2b
* feat: add RBAC viewer accounts, atomic deployments, and fleet-wide backups (Pro) Introduces three Pro-tier features: - RBAC: Multi-user system with admin/viewer roles, user management UI, automatic migration from single-admin credentials, viewer restrictions across the entire UI (read-only editor, hidden action buttons) - Atomic Deployments: Pre-deploy file backup to .sencho-backup/, automatic rollback on health probe failure, manual rollback button, health probes added to stack updates, webhook-triggered deploys use atomic rollback - Fleet-Wide Backups: Point-in-time snapshots of compose files across all nodes (local + remote), stored centrally in SQLite, per-stack restore with optional redeploy, graceful handling of offline nodes * fix(settings): use correct ProGate prop name in UsersSection * fix(settings): remove unused isPro prop from UsersSection * fix(auth): fetch user info after login and setup so isAdmin is set correctly * feat(pricing): revise pricing strategy and enforce variant-based seat limits Raise Personal Pro from $49/yr to $69/yr with 3 viewer seats (up from 1). Add $15/mo billing option for Team Pro. Mark lifetime pricing as a 90-day early-adopter offer. Store Lemon Squeezy variant_name on activation/validation and enforce seat limits server-side per variant. * feat(licensing): add Lemon Squeezy checkout, webhook, and billing portal integration Server-side checkout URL generation (POST /api/checkout) with admin email pre-fill and instance_id custom data. HMAC-SHA256 verified webhook endpoint (POST /api/webhooks/lemonsqueezy) handling order, subscription, and payment lifecycle events for automatic license activation. Customer billing portal link stored from webhook events and exposed via GET /api/billing/portal. In-app checkout buttons in Settings with manual license key fallback. * fix(licensing): exempt Lemon Squeezy webhook from auth middleware The catch-all auth middleware on /api/* was blocking the public webhook endpoint. Added /webhooks/lemonsqueezy to the exemption list alongside /auth/* and /webhooks/:id/trigger. * feat(pricing): update pricing to final live rates Personal Pro: $7.99/month, $69.99/year, $249 lifetime. Team Pro: $49.99/month, $499.99/year, $1,499 lifetime. Added personal_monthly checkout variant across backend, frontend, and website. * refactor(licensing): remove server-side checkout/webhook for self-hosted model Sencho is self-hosted — each user runs their own instance, so there is no central server to receive webhooks or hold the store API key. Replaced in-app checkout buttons with a "View Pricing" redirect to sencho.io and kept manual license key activation as the primary flow. - Delete LemonSqueezyService (checkout, webhook, HMAC verification) - Remove POST /api/checkout, GET /api/billing/portal, POST /api/webhooks/lemonsqueezy - Remove raw body parser and auth exemption for webhook route - Remove all LEMONSQUEEZY_* env vars from .env.example - Replace checkout buttons in SettingsModal with single "View Pricing" button - Simplify LicenseContext checkout to open sencho.io pricing page - Update licensing docs to reflect website-based purchase flow * chore: normalize em-dashes to hyphens across codebase (linter) * chore: remove accidentally tracked directories from index
61 lines
2.6 KiB
Plaintext
61 lines
2.6 KiB
Plaintext
---
|
|
title: Dashboard
|
|
description: Real-time system stats, historical metrics, and a quick-start converter for your host machine.
|
|
---
|
|
|
|
The **Home** tab is the first thing you see after logging in. It shows a live snapshot of your host's health alongside container activity across all stacks.
|
|
|
|
<Frame>
|
|
<img src="/images/dashboard/dashboard-overview.png" alt="Sencho dashboard showing container stats, system stats, and historical charts" />
|
|
</Frame>
|
|
|
|
## Container stats
|
|
|
|
The top row summarises container state at a glance:
|
|
|
|
| Card | What it shows |
|
|
|------|---------------|
|
|
| **Active Containers** | Running containers - broken down as `N managed · N external` |
|
|
| **Exited Containers** | Stopped or crashed containers |
|
|
| **Docker Network** | Current inbound/outbound network throughput across all containers |
|
|
|
|
**Managed** means the container belongs to a stack in your `COMPOSE_DIR`. **External** means it exists on the Docker host but was started outside Sencho (e.g. by another Compose project or `docker run`).
|
|
|
|
## System stats
|
|
|
|
The second row shows host-level resource usage, polled every few seconds:
|
|
|
|
| Card | What it shows |
|
|
|------|---------------|
|
|
| **Host CPU** | Current CPU usage percentage and core count |
|
|
| **Host RAM** | Used / total memory in GB and percentage |
|
|
| **Host Disk** | Used / total disk space for the primary mount point |
|
|
|
|
When any value exceeds configured thresholds (set in **Settings → System Limits**), the card changes colour as a visual warning.
|
|
|
|
## Historical metrics charts
|
|
|
|
Two area charts display time-series data sampled at one-minute intervals, retained for up to 24 hours (configurable in **Settings → Developer**):
|
|
|
|
- **Normalized CPU Usage** - total CPU percentage across all managed containers, normalised over all host cores
|
|
- **Normalized RAM Usage** - total memory allocated by managed containers, in GB
|
|
|
|
The x-axis shows time labels. Hover over a data point to see the exact value at that moment.
|
|
|
|
<Note>
|
|
Charts only show data from the moment Sencho started. If you just installed Sencho, they will be mostly empty until metrics accumulate.
|
|
</Note>
|
|
|
|
## Convert `docker run` to Compose
|
|
|
|
The bottom panel provides a quick converter: paste any `docker run` command and Sencho transforms it into a valid `docker-compose.yaml` snippet.
|
|
|
|
```bash
|
|
# Example input
|
|
docker run -d --name myapp -p 8080:80 -e TZ=UTC -v /data:/app/data nginx:latest
|
|
```
|
|
|
|
Click **Convert** and the output YAML appears ready to copy. You can then create a new stack and paste it into the editor.
|
|
|
|
This is useful when migrating existing containers to managed Compose stacks without having to write YAML by hand.
|