Studio-Saelix/sencho：README 來源編輯指南

Studio-Saelix/sencho 的 README 將專案描述為「Self-hosted Docker Compose management platform. For single or multi-host compose-first workflow.」。本文只整理倉庫可直接核對的內容，不把 star、Fork 或宣傳語當成品質證明。README 在「Self-hosted Docker Compose management for one machine or a fleet.」下寫到：> [!NOTE] > Sencho is used in production for day-to-day Docker Compose and fleet management. As a pre-1.0 project it still evolves quickly, so review the known limitations and validate against your own setup before deploying it on critical。這說明的是專案邊界，不是已完成的生產驗證。

從 README 的「Stacks」與相關條目，可以先判斷它是否處理你的實際問題：Atomic deployments with automatic rollback on failure。若需求不同，不應只因專案熱度就採用。本文保留原始專案名、命令與元件名，方便回到一手來源核對。 README 另外列出一項可核對的資訊：Full Compose lifecycle: create, deploy, restart, stop, take down, pull。這類原文條目可用來設計試跑步驟，但不能取代實際環境測試。

README 將運作方式分散在「What Sencho is」等段落。可確認的線索包括：It runs as a single container on your hardware and provides a UI for common Compose operations: deploying, editing files, watching logs, restarting containers, browsing volumes, and recovering from failures.。本文不把未寫出的架構、效能或安全邊界補成結論；真正的執行鏈仍要配合目錄、設定檔與版本標籤檢查。

第一次安裝應從 README 指出的入口開始。目前可核對的命令是： services: sencho: image: saelix/sencho:latest container_name: sencho restart: unless-stopped ports: - "1852:1852" volumes: - /var/run/docker.sock:/var/run/docker.sock - ./data:/app/data # 1:1 Compose Path Rule: the host path MUST match the container path - /opt/docker:/opt/docker environment: - COMPOSE_DIR=/opt/docker - DATA_DIR=/app/data 如果倉庫沒有命令，本文不會自行編造步驟，而是建議先閱讀「What Sencho is」，確認系統依賴、預設埠與首次初始化。

日常使用取決於專案文件。README 的「What Sencho is」段落提到：Multi-node was part of the architecture from the start, not bolted on later: every Sencho instance is the same autonomous node, whether it runs alone or as one of many in a fleet.。設定檔、環境變數、權限與資料目錄只在來源明確時才會記錄；沒有寫出的預設值，應在測試環境驗證並保留回滾副本。 同一部分也提到：Monaco editor with diff preview before save and one-click rollback to any prior deploy。