Nginx-location-configuration

  • Done
  • quality assurance status badge
Details
2 participants
  • Andreas Enge
  • Clément Lassieur
Owner
unassigned
Submitted by
Andreas Enge
Severity
normal

Debbugs page

A
A
Andreas Enge wrote on 10 Jan 2018 10:46
(address . bug-guix@gnu.org)
20180110184634.GA11128@jurong
Hello,

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

Andreas
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(-)

Toggle diff (22 lines)
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
C
C
Clément Lassieur wrote on 14 Jan 2018 10:59
control message for bug #30071
(address . control@debbugs.gnu.org)
87d12cqnak.fsf@lassieur.org
tags 30071 fixed
close 30071
?
Your comment

This issue is archived.

To comment on this conversation send an email to 30071@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 30071
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch