Hi, "Tanguy Le Carrour" <[email protected]> writes:
> Bonjour Edouard, > > > On Wed Jan 21, 2026 at 7:28 AM CET, Edouard Klein wrote: >> I don't know if my method is in line with the correcr way, but you can find >> inspiration from: >> >> Https://gitlab.com/edouardklein/guix/-/blob/beaverlabs/beaver/packages/python-xyz.scm?ref_type=heads#L884 > > 😲… oooh… 😱! > I could not have come up with that solution on my own! Thaaaaaanks, you saved > my day!! 🥳 > > Even if I’m **really** grateful, I have to say that I don’t really like the > fact > that I have to create a "runner script", but as long as it works! 😅 > #pragmatism > > If someone has a way to start `gunicorn` "inside the context of a profile" > directly > from the Shepherd service, I’d be more that happy to give it a try. It's something I had to do recently for the luanti-service-type, where I wished I could simply generate a full-fledged profile from the service instead of building the required environment variable manually, MacGyver style (see how the LUANTI_MOD_PATH environment variable is computed in commit 47af617b5cc). I think it'd make sense to be able to compute and use a service-specific profile in a service, which would help in this kind of situation, though I haven't pondered yet *how* exactly this could be implemented. -- Thanks, Maxim
