From: Felix Lechner via <help-guix@gnu.org>
To: Jesse Millwood <jesse_m@fastmail.com>
Cc: help-guix@gnu.org
Subject: Re: Debugging Shepherd Daemon. Possible escape char issue.
Date: Fri, 29 Nov 2024 13:25:25 -0800 [thread overview]
Message-ID: <87plmdg2be.fsf@lease-up.com> (raw)
In-Reply-To: <e3e91f86-dab4-488e-8259-8a00e424d5e4@fastmail.com> (Jesse Millwood's message of "Fri, 29 Nov 2024 14:08:12 -0500")
Hi Jesse,
On Fri, Nov 29 2024, Jesse Millwood wrote:
> "traefik.http.routers.whoami.rule=Host\(\\\"whoami.geekslab\\\")"
It's a bit of a long short, but I might try:
> "traefik.http.routers.whoami.rule=Host(\"whoami.geekslab\")"
I dropped the escape from the opening parenthesis \( which which worked
on Geiser but seemed not needed.
Perhaps more significantly, I also the dropped escape character \\
before each of the escaped quotes because I'm not sure the Shepherd
offers shell expansion.
Kind regards
Felix
next prev parent reply other threads:[~2024-11-29 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 19:08 Debugging Shepherd Daemon. Possible escape char issue Jesse Millwood
2024-11-29 21:25 ` Felix Lechner via [this message]
2024-11-29 23:52 ` Jesse Millwood
2024-12-10 12:11 ` Jesse Millwood
2024-12-10 13:17 ` Jesse Millwood
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87plmdg2be.fsf@lease-up.com \
--to=help-guix@gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=jesse_m@fastmail.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).