From: Tobias Geerinckx-Rice <me@tobias.gr>
To: guix-devel@gnu.org
Subject: Fixing Zabbix db-secret-file documentation.
Date: Fri, 06 Nov 2020 14:29:14 +0100 [thread overview]
Message-ID: <87tuu2bolx.fsf@nckx> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 615 bytes --]
Guix,
We currently claim that db-secret-file is appended to
zabbix.conf.php.
To me that can only mean:
$ cat db-secret-file
$DB['PASSWORD'] = 'supersecure'
$DB['maybe'] = 'some more sekrit stuff too'
but it's really just:
"$DB['PASSWORD'] = '" (with-input-from-file db-secret-file
read-string) "';"
It's late into 1.2 to invalidate manual translations. However,
I'm sceptical of shipping a translated-but-IMO-incorrect snippet
over a better English one just to boost coverage stats, and would
like to push it anyway. Thoughts?
Kind regards,
T G-R
[-- Attachment #1.2: 0001-doc-Better-document-Zabbix-db-secret-file.patch --]
[-- Type: text/x-patch, Size: 1340 bytes --]
From c6746726e4db7f674297de79ae599ca9686658a1 Mon Sep 17 00:00:00 2001
From: Tobias Geerinckx-Rice <me@tobias.gr>
Date: Fri, 6 Nov 2020 13:17:00 +0100
Subject: [PATCH 1/2] =?UTF-8?q?doc:=20Fix=20Zabbix=20?=
=?UTF-8?q?=E2=80=98db-secret-file=E2=80=99=20documentation.?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
* doc/guix.texi (Monitoring Services): Document ‘db-secret-file’'s (lack
of) structure and gexp support.
---
doc/guix.texi | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/guix.texi b/doc/guix.texi
index 217ed7a8a8..1c29799d6c 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -22168,9 +22168,10 @@ Defaults to @samp{""}.
@end deftypevr
@deftypevr {@code{zabbix-front-end-configuration} parameter} string db-secret-file
-Secret file which will be appended to @file{zabbix.conf.php} file. This
-file contains credentials for use by Zabbix front-end. You are expected
-to create it manually.
+Secret file containing the credentials for the Zabbix front end. The value
+must be a local file name, not a G-expression. You are expected to create
+this file manually. Its contents will be copied into @file{zabbix.conf.php}
+as the value of @code{$DB['PASSWORD']}.
Defaults to @samp{""}.
--
2.29.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next reply other threads:[~2020-11-06 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 13:29 Tobias Geerinckx-Rice [this message]
2020-11-07 12:19 ` Fixing Zabbix db-secret-file documentation Oleg Pykhalov
2020-11-07 12:47 ` Tobias Geerinckx-Rice
2020-11-08 0:48 ` Miguel Ángel Arruga Vivas
2020-11-08 23:27 ` Tobias Geerinckx-Rice
2020-11-09 11:54 ` Miguel Ángel Arruga Vivas
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=87tuu2bolx.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-devel@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).