From 415a3d9efe62e0ce303353a5dbe3dfed3b520857 Mon Sep 17 00:00:00 2001
From: "Sergey A. Osokin" <osa@FreeBSD.org>
Date: Sun, 7 Oct 2018 16:18:58 +0000
Subject: [PATCH] Add another package message file to fix the issue with it for
 nginx flavor.

Bump PORTREVISION.

PR:	231877
---
 www/rubygem-passenger/Makefile                   |  3 ++-
 .../{pkg-message.in => pkg-message-apache.in}    |  0
 www/rubygem-passenger/files/pkg-message-nginx.in | 16 ++++++++++++++++
 3 files changed, 18 insertions(+), 1 deletion(-)
 rename www/rubygem-passenger/files/{pkg-message.in => pkg-message-apache.in} (100%)
 create mode 100644 www/rubygem-passenger/files/pkg-message-nginx.in

diff --git a/www/rubygem-passenger/Makefile b/www/rubygem-passenger/Makefile
index d987ee610183..b97fa874f25d 100644
--- a/www/rubygem-passenger/Makefile
+++ b/www/rubygem-passenger/Makefile
@@ -3,6 +3,7 @@
 
 PORTNAME=	passenger
 PORTVERSION=	5.3.5
+PORTREVISION=	1
 CATEGORIES=	www rubygems
 MASTER_SITES=	RG
 PKGNAMEPREFIX=	rubygem-
@@ -60,7 +61,7 @@ BUILD_DEPENDS+=	rubygem-rack>=0:www/rubygem-rack
 RUN_DEPENDS:=	${BUILD_DEPENDS}
 
 SUB_LIST+=	GEM_LIB_DIR=${GEM_LIB_DIR} RUBY=${RUBY}
-SUB_FILES=	pkg-message
+SUB_FILES=	pkg-message-${FLAVOR}
 
 PLIST_FILES=	bin/passenger \
 		bin/passenger-config \
diff --git a/www/rubygem-passenger/files/pkg-message.in b/www/rubygem-passenger/files/pkg-message-apache.in
similarity index 100%
rename from www/rubygem-passenger/files/pkg-message.in
rename to www/rubygem-passenger/files/pkg-message-apache.in
diff --git a/www/rubygem-passenger/files/pkg-message-nginx.in b/www/rubygem-passenger/files/pkg-message-nginx.in
new file mode 100644
index 000000000000..e79125579daf
--- /dev/null
+++ b/www/rubygem-passenger/files/pkg-message-nginx.in
@@ -0,0 +1,16 @@
+#####################################################################
+
+Please edit your nginx configuration file, and add these lines:
+
+   server {
+       root %%PASSENGER_INSTALL_DIR%%;
+       passenger_enabled on;
+       passenger_ruby %%RUBY%%;
+       passenger_sticky_sessions on;
+   }
+   
+After you restart nginx, you are ready to deploy any number of Ruby on Rails
+applications on nginx, without any further Ruby on Rails-specific
+configuration!
+
+#####################################################################