You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a puppet module (that is far from ready for human consumption) to setup Nginx, passenger, rails, etc... following the example that RVM has for Apache. I am still using this RVM module for all things RVM. I just copied the passenger section to my own module and modified it to work for nginx. One problem that I recently had was how to select a specific version of the passenger gem to run the "passenger-install-nginx" from...
... and all was well until one day I changed the yaml file that selects the passenger version (in error, but whatever) to a lower version number (4.0.41 instead of 4.0.45 or whatever). The problem was that each time puppet ran, it would try to re-run the passenger-install-nginx-module because it was specifically looking for 4.0.41, and each time it ran that exec, it would select the newest version.
Consider this is probably a support request for an RVM/ruby novice ;)
~tommy
The text was updated successfully, but these errors were encountered:
I think the "subscribe" line is unneeded, another developer added that to attempt to detect ruby version changes... I added the "unless .... grep -q ${passenger_module}" part.. as that checks both ruby version and passenger module.
I think I could just do something like ${rvm_prefix}gems/${passenger_module}/bin/passenger-install-nginx_module ... but that "feels" wrong somehow? Is it?
Speaking of which, how does your apache version detect ruby/passenger version changes to recompile the module?
I have a puppet module (that is far from ready for human consumption) to setup Nginx, passenger, rails, etc... following the example that RVM has for Apache. I am still using this RVM module for all things RVM. I just copied the passenger section to my own module and modified it to work for nginx. One problem that I recently had was how to select a specific version of the passenger gem to run the "passenger-install-nginx" from...
I have something that looks like:
... and all was well until one day I changed the yaml file that selects the passenger version (in error, but whatever) to a lower version number (4.0.41 instead of 4.0.45 or whatever). The problem was that each time puppet ran, it would try to re-run the passenger-install-nginx-module because it was specifically looking for 4.0.41, and each time it ran that exec, it would select the newest version.
Consider this is probably a support request for an RVM/ruby novice ;)
~tommy
The text was updated successfully, but these errors were encountered: