Add a comparison to Portable Services
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 38
- Forks
- 1
- Avg merge
- 1h 53m
- Merged PRs (30d)
- 13
Description
Systemd has Portable Services and flakelet seems very similar in goals
I think the big difference is that on a system with a /nix/store we don't need RootImage=/RootDirectory= like with Portable Services
I think it would be useful to at least call it out in docs that this is very similar to them.
A few things that Portable Services do that we could also add to this:
- Portable services link to
/run/systemd/system.attachedto distinguish them from "normal" system units - Portable services come with a
--profileflag that allows you to conveniently provision drop-ins with a preset of systemd hardening options - Id adds a
LogExtraFields=PORTABLE_ROOT=<path to portable service>so you can identify journal logs coming from a portable service
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing flakelet documentation alongside the linked systemd Portable Services documentation. Document the similarities and the /nix/store distinction; treat the attachment marker, profile, and LogExtraFields ideas as separate follow-up scope unless maintainers define them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100