If I may have a feature request, it would probably be some sort of “migration” function to docker/docker-compose/helm
This is an interesting idea. It probably is in line with something I want to implement/collaborate with someone on: “Portable service layer”. The idea originated after Question: How to use `systemd.service` ? · Issue #239 · juspay/services-flake · GitHub, but turns out there was already a draft for something similar in nixpkgs.
This is what I think the future for services would look like:
Option definitions will lie in nixpkgs along with config for systemd service, which it already does, but won’t be as tightly coupled after “Portable service layer” is implemented. services-flake can then re-use the options from nixpkgs, and output configs for multiple targets, like: lanuchd, process-compose or as you mentioned docker/docker-compose/helm. Thus, we will have uniformity in option definitions no matter what the underlying service management mechanism one uses.