Repository navigation
feat(desktop): manage installed remote Runtime Host services #3281
Description
English
Problem
Desktop can add and connect to a managed remote Runtime Host, but ongoing service management still requires using the CLI on the Host. Users cannot inspect the installed release, service state, configured directory roots, or recent service logs from the computer entry, and repair or clean uninstall are easy to confuse with removing the Desktop Profile or deleting Host data.
Desired outcome
Add a per-Host management surface for SSH-managed computers that can:
- show the installed release, service state, configured directory roots, and bounded recent logs;
- start or restart the service, reopen the existing setup flow for repair, and cleanly uninstall the Maka-managed service and package;
- preserve the State Root and Desktop Profile during uninstall, with those ownership boundaries stated before confirmation.
Direct connection Profiles should remain usable, but service management should be unavailable when no SSH management channel exists. This slice should reuse the existing service and setup authorities and should not introduce an updater or credential-management state machine.
Alternatives or workarounds
Today, users SSH to the remote computer and run maka runtime-host service ... commands manually.
Refs #3228
中文
问题
Desktop 已能添加并连接由 Maka 管理的 remote Runtime Host，但后续服务管理仍要求用户进入 Host 手工运行 CLI。用户无法从电脑条目查看已安装版本、服务状态、配置的目录根或近期日志；修复、干净卸载、移除 Desktop Profile 和删除 Host 数据之间的边界也不够清楚。
期望结果
为通过 SSH 管理的电脑增加 per-Host 管理界面：
- 显示已安装版本、服务状态、配置的目录根和有界的近期日志；
- 启动或重启服务，复用现有 setup 流程进行修复，并干净卸载 Maka 管理的 service 与 package；
- 卸载时保留 State Root 与 Desktop Profile，并在确认前明确这些所有权边界。
Direct connection Profile 仍可正常使用，但没有 SSH 管理通道时不提供服务管理。本阶段复用已有 service 与 setup authority，不引入 updater 或 credential 管理状态机。
替代方案或当前做法
目前用户只能 SSH 到远端电脑，手工运行 maka runtime-host service ... 命令。
Refs #3228
Activity