service_manager: Docker-action support (hero_onlyoffice) #98

New issue

Open

opened 2026-05-07 19:12:40 +00:00 by mik-tf · 0 comments

mik-tf commented

2026-05-07 19:12:40 +00:00

Owner

Tracked from #90.

hero_onlyoffice is a Docker container, not a Rust service. The upstream nu module service_onlyoffice.nu runs:

docker run for the OnlyOffice DocumentServer image (onlyoffice/documentserver:9.3.1)
docker stop && docker rm in kill_other (custom action: field)
process_filters: ['docker run --name onlyoffice']

The v2 manager's actions all use interpreter: "exec" and run binaries from ~/hero/bin/. There's no path for Docker actions today.

Fix: add a docker-shaped HeroService impl that emits a hero_proc action with script: "docker run ...", kill_other.action for cleanup, and process_filters. May need a small helper in lib.

Excluded from the v2 registry until this is implemented (see services/mod.rs doc comment).

Tracked from #90. `hero_onlyoffice` is a Docker container, not a Rust service. The upstream nu module `service_onlyoffice.nu` runs: - `docker run` for the OnlyOffice DocumentServer image (onlyoffice/documentserver:9.3.1) - `docker stop && docker rm` in kill_other (custom `action:` field) - process_filters: `['docker run --name onlyoffice']` The v2 manager's actions all use `interpreter: "exec"` and run binaries from `~/hero/bin/`. There's no path for Docker actions today. **Fix**: add a docker-shaped `HeroService` impl that emits a hero_proc action with `script: "docker run ..."`, `kill_other.action` for cleanup, and process_filters. May need a small helper in lib. Excluded from the v2 registry until this is implemented (see `services/mod.rs` doc comment).