Thank you Maxime for your answer :)
Maxime Devos writes:
> e...@beaver-labs.com schreef op zo 11-04-2021 om 21:31 [+0200]:
>> Dear fellow Guixers,
>
>> [...]
>> But, when I try to run it with shepherd, it fails because it can't find
>> flask (a dependency of the software, which I've put as a
>> p
e...@beaver-labs.com schreef op zo 11-04-2021 om 21:31 [+0200]:
> Dear fellow Guixers,
> [...]
> But, when I try to run it with shepherd, it fails because it can't find
> flask (a dependency of the software, which I've put as a
> propagated-input, and is indeed installed in the container).
Propag
Hi !
I did, thanks :) But this post talks only about shepherd, not its
integration with guix. It is indeed a very good resource for creating
shepherd services, and I was able thanks to it to write a shepherd
service.
What I would like to do is create a shepherd service, using some
facilities offe
Did you read this blog post?:
https://guix.gnu.org/en/blog/2020/gnu-shepherd-user-services/
== START
The GNU Shepherd manual suggests putting all the services inside a monolithic
init.scm file, located by default at $XDG_CONFIG_DIR/shepherd/init.scm. While
this does make it easy to
Hi,
So I looked at the source and I understand that there's no way around
having only PATH=/run/current-system/profile/bin as the sole environment
of a service (which makes me wonder how anyone is running any service in
GuixSD, don't you need any env variables ?).
I tried to define a trivial pack
Dear fellow Guixers,
I'm trying to create an operating system declaration, so that I can run
a piece of software of mine in a container with =guix system container=.
I wrote a package for the software. The package works: the tests pass
and when the package is installed I can run the software.
I
