This is where it started
“Add enough services to your own server, and eventually you lose track of what you even built.”observed → Started 2026.07.03
— So we built
my-systemd
Livetoolsnpm package
A tiny CLI for finding and grouping the systemd services you created.
Developer evidence
What I owned in this project
- Period
- 2026.07 – Operating now
- Team
- Solo developer
- Contribution
- Planning · design · development · deployment · operations, 100%
- Owned scope
- Uses a dependency-free Node CLI that separates service discovery, systemctl/journalctl wrappers, canonical group config, and guarded batch actions.
Introduction
my-systemd finds the systemd services you created on a VPS or home server and shows their status and logs. Save frequently used services as groups, and review control commands with a dry run before execution.
User flow
- 01
Run `my-svcs` to see candidate services and their system/user scopes together.
- 02
Group frequently watched services with commands like `my-svcs group create web @1 @4`.
- 03
Check group status and doctor output, then execute control commands only after reviewing the dry-run plan.
Highlights
- Prioritizes local service files you created instead of distro/vendor units.
- Saves frequently used services as reusable groups.
- Keeps batch start, stop, and restart dry-run by default to prevent accidental control actions.