-
-
Notifications
You must be signed in to change notification settings - Fork 883
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manage libnginx-mod-http-passenger on modern Debian / Ubuntu #1376
Conversation
On Debian 9 & Ubuntu 18.04 libnginx-mod-http-passenger needs to be installed instead of passenger according to the installation guide by passenger. libnginx-mod-http-passenger has a dependency on passenger, so it will be installed. Without libnginx-mod-http-passenger nginx will not be able to handle passenger. Installation guide: https://www.phusionpassenger.com/docs/tutorials/deploy_to_production/installations/oss/ownserver/ruby/nginx/
nginx::config is a classThe enclosing module is declared in 11 of 578 indexed public Puppetfiles. Breaking changes to this file MAY impact these modules (near match):
The enclosing module is declared in 11 of 578 indexed public Puppetfiles. Breaking changes to this file WILL impact these modules (exact match):
Breaking changes to this file MAY impact these modules (near match):
The enclosing module is declared in 11 of 578 indexed public Puppetfiles. that may have no external impact to Forge modules. nginx::package::redhat is a classThe enclosing module is declared in 11 of 578 indexed public Puppetfiles. that may have no external impact to Forge modules. nginx::params is a classThe enclosing module is declared in 11 of 578 indexed public Puppetfiles. Breaking changes to this file MAY impact these modules (near match): These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report. Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only. |
Now that we install the proper package on recent Debian/Ubuntu, check for the good package in the catalog.
I'm not sure if this is a backwards-incompatible release or not. What about those newer Debian versions if they currently try to use the module? Doesn't it work at all? What happens if the module installed the passanger package in the past and now install the new package? Does that work at all? |
Back from holidays, sorry for the delay! The Per se, the previous behavior is working from the Puppet point of view, but the resulting configuration is not working (because the nginx module is not installed nor configured). My guess is that this would only require a MINOR version bump: the change is backward compatible but adds support for systems previously unsupported. Thanks! |
Manage libnginx-mod-http-passenger on modern Debian / Ubuntu
Pull Request (PR) description
This is a follow-up to #1341 (closed without being merged) which was an attempt to fix #1340. I took the commits in this legacy PR, rebased them on top of master (fixing a bunch of conflicts) and am now fixing the CI.
This Pull Request (PR) fixes the following issues
Fixes #1340