feat: Portable services

[shivaraj-bh]

resolves #354

Init with ollama.

Usage

process-compose app

# Inside perSystem
{
  process-compose.sf-ollama = {
    imports = [ inputs.services-flake.processComposeModules.default ];
    services.ollama.”o1”.enable = true;
  };
}

And nix run .#sf-ollama to start the service

systemd/launchd user unit/agent

Note: The option services.<service-name> overlaps with existing service definitions in home-manager. I could rename it to avoid conflict, but for now you could use the release-24.11 branch of home-manager that doesn’t yet have ollama.

# In your `homeConfiguration`
{
  imports = [ inputs.services-flake.homeModules.default ];
  services.ollama.”o1”.enable = true;
}

Lastly, activate your home-manager config...

<Insert home-manager template to test Ollama running via systemd or launchd>

TODO:

• outputs.{systemd, launchd, process-compose} must share as much configuration as possible (also add sane defaults for systemd and launchd)
• systemd and launchd tests
• Documentation

[Eveeifyeve]

I like the idea of this pr although it would conflict with home-manager. So I would say maybe rename to services-flake.services? Yes it would break compatibility but it would be the best to solve this situation.