Bug 231877 - www/rubygem-passenger with FLAVOR=nginx wrong post install information
Summary: www/rubygem-passenger with FLAVOR=nginx wrong post install information
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Sergey A. Osokin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-02 13:13 UTC by Michael Kastner
Modified: 2018-10-07 16:20 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (osa)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Kastner 2018-10-02 13:13:43 UTC
When building www/rubygem-passenger with

make FLAVOR=nginx install

the concluding information points to the wrong (i.e. apache) module:

Quote begin ----

Please edit your Apache configuration file, and add these lines:

   LoadModule passenger_module /usr/local/lib/ruby/gems/2.4/gems/passenger-5.3.5/buildout/apache2/mod_passenger.so
   PassengerRoot /usr/local/lib/ruby/gems/2.4/gems/passenger-5.3.5
   PassengerRuby /usr/local/bin/ruby24

After you restart Apache, you are ready to deploy any number of Ruby on Rails
applications on Apache, without any further Ruby on Rails-specific
configuration!

Quote end   ----

It should point to the nginx module, which is located here after passenger installation:

/usr/local/libexec/nginx/ngx_http_passenger_module.so
Comment 1 commit-hook freebsd_committer 2018-10-07 16:19:17 UTC
A commit references this bug:

Author: osa
Date: Sun Oct  7 16:18:59 UTC 2018
New revision: 481455
URL: https://svnweb.freebsd.org/changeset/ports/481455

Log:
  Add another package message file to fix the issue with it for nginx flavor.

  Bump PORTREVISION.

  PR:	231877

Changes:
  head/www/rubygem-passenger/Makefile
  head/www/rubygem-passenger/files/pkg-message-apache.in
  head/www/rubygem-passenger/files/pkg-message-nginx.in
  head/www/rubygem-passenger/files/pkg-message.in
Comment 2 Sergey A. Osokin freebsd_committer 2018-10-07 16:20:15 UTC
The issue has been fixed.