bug#30069: Nginx-location-configuration

[Andreas Enge <andreas@enge.fr>]

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

Hello,

the attached patch attempts to correct a documentation bug for the nginx
service. Do people who know the service better agree?

Andreas


[-- Attachment #2: 0001-doc-Correct-documentation-of-NGINX-LOCATION-CONFIGUR.patch --]
[-- Type: text/plain, Size: 1214 bytes --]

From 3c593d426ce726f6585d736ff27dee59ac081c57 Mon Sep 17 00:00:00 2001
From: Andreas Enge <andreas@enge.fr>
Date: Wed, 10 Jan 2018 19:41:32 +0100
Subject: [PATCH] doc: Correct documentation of NGINX-LOCATION-CONFIGURATION.

* doc/guix.texi (Web Services): The body of an NGINX-LOCATION-CONFIGURATION
is a list of strings and not a string.
---
 doc/guix.texi | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index e9ee5127a..c3ce05f79 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -15107,11 +15107,12 @@ URI which this location block matches.
 
 @anchor{nginx-location-configuration body}
 @item @code{body}
-Body of the location block, specified as a string. This can contain many
+Body of the location block, specified as a list of strings. This can contain
+many
 configuration directives.  For example, to pass requests to a upstream
 server group defined using an @code{nginx-upstream-configuration} block,
-the following directive would be specified in the body @samp{proxy_pass
-http://upstream-name;}.
+the following directive would be specified in the body @samp{(list "proxy_pass
+http://upstream-name;")}.
 
 @end table
 @end deftp
-- 
2.15.1