It's easier to generate a package that wraps the script binary and then use
it in a cronjob
On Wed, Oct 7, 2015 at 11:17 PM, Bjørn Forsman
wrote:
> On 7 October 2015 at 22:06, Anders Lundstedt
> wrote:
> > A python script I have depends on
On 8 October 2015 at 09:18, Domen Kožar wrote:
> It's easier to generate a package that wraps the script binary and then use
> it in a cronjob
Or just "nix-shell ... --run "NIX_REMOTE=daemon ./my-script.py"?
- Bjørn
___
nix-dev mailing
write a wrapper-script like this below:
#!/run/current-system/sw/bin/bash
source /etc/profile
nix-shell --pure -p python3 -p python3Packages.requests2 --run
./my-script.py
two options from here:
* but as domen already said, maybe you generate your own 'program' as a
store entry
* or you
Hi,
On 08/10/15 09:23, Bjørn Forsman wrote:
> On 8 October 2015 at 09:18, Domen Kožar wrote:
>> It's easier to generate a package that wraps the script binary and then use
>> it in a cronjob
>
> Or just "nix-shell ... --run "NIX_REMOTE=daemon ./my-script.py"?
Surely that should
On 8 October 2015 at 14:48, Eelco Dolstra wrote:
> Hi,
>
> On 08/10/15 09:23, Bjørn Forsman wrote:
>
>> On 8 October 2015 at 09:18, Domen Kožar wrote:
>>> It's easier to generate a package that wraps the script binary and then use
>>> it in a cronjob
>>
Hi,
On 08/10/15 15:07, Bjørn Forsman wrote:
> Right :-)
>
> But don't forget that NIX_REMOTE isn't part of
> config.environment.sessionVariables.
Good point. Also I forgot that you need
path = [ pkgs.nix ];
It's easier to do
script = "source /etc/profile; nix-shell -p ..."
but that
@roconnor: Hey!
$ nix-store --read-log /run/current-system/sw
prints a whole bunch of 'collision between' lines, but when I pipe it into
grep it returns nothing for 'agda' or 'Agda'
The file pointed to by
$ nix-store -q -deriver /run/current-system/sw
Has four references to Agda. Two to the
On Thu, 8 Oct 2015 00:03:23 +0200
Kamil Chmielewski wrote:
> 2015-10-07 20:44 GMT+02:00 Bryan Gardiner :
>
> > > your shell does not find "./go-app".
> > > What does ls -l say?
> >
>
> The file path is right and exists for sure.
>
>
> > Most likely Kamil