all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: help-guix@gnu.org
Subject: Re: Privoxy user config without hard-coded GNU store path?
Date: Sun, 06 Oct 2019 14:46:49 +0200	[thread overview]
Message-ID: <871rvqghxi.fsf@ambrevar.xyz> (raw)
In-Reply-To: <20191006122245.GH561@E5400>

[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]

Hi Efraim!

Thanks for the suggestions!

> The simple solution here is to change the lines to 
> confdir /home/USER/.guix-profile/etc/privoxy
> logdir /home/USER/log/privoxy

Duh, that was easy! :p

> If you want an untested user shepherd service, here's one I've come up
> with on the spot:
>
> (define privoxy
>   (make <service>
>   #:provides '(privoxy)
>   #:docstring "Privoxy filters outgoing internet connections"
>   #:start (make-forkexec-constructor
>             '("/var/guix/profiles/per-user/USER/current-guix/bin/privoxy" "--no-daemon" "/home/USER/.config/privoxy/config")
>             #:log-file "/home/USER/log/privoxy/privoxy.log")
>   #:stop (make-kill-destructor)
>   #:respawn? #t))
> (register-services privoxy)

That's a good starting point, but furthermore what I meant was a service
in which we declare the configuration file, so that I don't need to
provide my own "config".

I guess that'd be another neat service to add to Shepherd/Guix ;)

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      reply	other threads:[~2019-10-06 12:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-06 11:51 Privoxy user config without hard-coded GNU store path? Pierre Neidhardt
2019-10-06 12:22 ` Efraim Flashner
2019-10-06 12:46   ` Pierre Neidhardt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871rvqghxi.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=efraim@flashner.co.il \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.