القائمة
Use when creating or reviewing Sermo Linux packaging, systemd units, OpenRC init scripts, Gentoo ebuilds, install paths, permissions, runtime directories, or service startup behavior.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | sermo-packaging |
| description | Use when creating or reviewing Sermo Linux packaging, systemd units, OpenRC init scripts, Gentoo ebuilds, install paths, permissions, runtime directories, or service startup behavior. |
You are the Linux packaging engineer for Sermo.
Use these defaults:
/usr/bin/sermoctl
/usr/sbin/sermod
/etc/sermo/
/usr/share/sermo/catalog/
/run/sermo/
/var/lib/sermo/
/var/log/sermo/ only if not using system logs
The systemd service should:
run sermod in foreground
use a dedicated config path
restart on failure if appropriate
create runtime directory where possible
use least privilege where practical
log to journald/stdout
Do not let systemd restart loops hide Sermo's own safety behavior.
The OpenRC init script should:
run sermod in foreground or supervise mode
use command_args for config path
support start/stop/status
create runtime directory
work on Gentoo/OpenRC
Think carefully about privilege.
Sermo may need root for service control and signaling. If future non-root access is added, it must go through explicit authorization and must not allow arbitrary command execution.
Potential artifacts:
packaging/systemd/sermod.service
packaging/openrc/sermod
packaging/gentoo/app-admin/sermo/sermo-9999.ebuild
packaging/debian/
make install is the canonical installer. It uses standard GNU directory
variables and DESTDIR staging, composed of granular targets: install-bin
(sermoctl→$(bindir), sermod→$(sbindir)), install-catalog (recursive,
preserving services/apps/libs/patterns), install-config (sample sermo.yml,
never overwriting an existing one; creates services, apps, notifiers, and watch
config directories: watches, networks, storages and mounts),
install-templates, install-tmpfiles,
install-systemd and install-openrc. The unit/init templates carry default /usr/bin/sermod and
/etc/sermo paths that install rewrites to the chosen $(sbindir) /
$(SERMO_CONFDIR). The catalog directory is compiled into the binaries as
$(SERMO_DATADIR)/catalog, and install-catalog installs that same tree; the
sample config's /usr/share/sermo and /etc/sermo paths are rewritten too, so
the install is relocatable. Variables: DESTDIR, PREFIX/prefix, bindir,
sbindir, datadir, sysconfdir, SYSTEMD_UNITDIR, OPENRC_INITDIR.
Review packaging with:
systemd-analyze verify packaging/systemd/sermod.service
shellcheck packaging/openrc/sermod
go test ./...
Use the best effort when tools are not available.
When working on packaging, return:
- files added/changed
- install paths
- service behavior
- permission assumptions
- validation commands run
Use when running safe Sermo validation or exploratory tests on remote Linux servers over SSH, using .env.ssh as the source of truth, local GOAMD64=v1 builds, staged all-host runs, temporary /tmp validation, or explicit remote installations under /etc/sermo. Covers active-services-only config, unsupported active-service reports, all safely discoverable host watches, dry-run deployments, storage under 5 percent free with 5G expand, fstab-backed local/network/USB mount units, Docker containers, libvirt/QEMU virtual machines, SMART daily, hdparm every 6h, Web UI on 0.0.0.0:9797 with startup/readiness/access timing, reusable scripts under scripts/remote-deploy, and safe alert/notification checks that must not execute hooks or alter server behavior.
Use when designing, editing, validating, merging, rendering, or reviewing Sermo YAML configuration, catalog services/apps/libs/patterns, services, mounts, clones, variables, checks, guards, locks, rules, or stop policies.
Use when implementing Go code for Sermo, especially CLI commands, internal packages, interfaces, command runners, config loading, checks, rules, locks, or operations.
Use when creating or reviewing Sermo service definitions for applications such as Apache, Nginx, Redis, MySQL, MariaDB, PostgreSQL, PHP-FPM, Postfix, Dovecot, HAProxy or similar services.
Use when writing or updating Sermo README, user guides, CLI docs, YAML examples, catalog service/app/lib/pattern documentation, rule documentation, safety documentation, or operations runbooks.
Use when adding or reviewing tests for Sermo, especially config resolution, backend detection, rule evaluation, locks, guards, process discovery, and safe operations.