Added support for passenger >= 4 #85
Conversation
The install script expects the home variable to be set. Choosing /tmp since we use it from puppet. Error: /usr/local/rvm/gems/ruby-1.9.3-p429/gems/passenger-4.0.5/lib/phusion_passenger/platform_info/ruby.rb:202:in `expand_path': non-absolute home (ArgumentError)
Sets a symlink with exec when the destination folder
${gempath}/passenger-${version}/ext/
does not exist. Also adapted compilation of library.
| exec { | ||
| 'create-symlink-for-passenger-4.0-modules': | ||
| command => "ln -s ${gempath}/passenger-${version}/libout/apache2/mod_passenger.so ${gempath}/passenger-${version}/ext/apache2/mod_passenger.so", | ||
| unless => "test -e ${gempath}/passenger-${version}/ext", |
There was a problem hiding this comment.
On my system, the ext directory exists, causing this symlink to not be created. The mod_passenger.so does exist in the buildout directory. Can we just change the generated Apache config to point to that if the version is >= 4.0.0?
There was a problem hiding this comment.
I did a pull request solving this in the template file for the Apache conf.d file (based on what was already there for the previous "ext" to "libout" changes). That may be a better method as it just uses the correct path in the LoadModule line. https://github.com/blt04/puppet-rvm/pull/89/files
I am also experiencing this issue when I attempt to install passenger. I'm on Ubuntu 12.04, Ruby 2.0.0p353, Passenger 4.0.33. Any ideas how I might get around this? |
|
I cloned the repo from @inetdavid and it worked. |
The install script for passenger >= expects the home variable to be set. Choosing /tmp
since we use it from puppet.
Error:
Also added a symlink since passenger changed the bin directory from
to