Dev env for 1.2

Development
#1

Hi! It looks like I need to be on ruby 1.9.3 for 1.2? Is that right?

And my httpd/conf.d/passenger.conf files need to change to reflect that?

Are you guys using rvm? I can't seem to get passenger to work with 1.9.3 . . .
passenger.conf :
LoadModule passenger_module modules/mod_passenger.so
<IfModule mod_passenger.c>
#PassengerRoot /usr/share/rubygems/gems/passenger-3.0.17
#PassengerRuby /usr/bin/ruby
PassengerRoot /usr/share/rubygems/gems/passenger-3.0.17
PassengerRuby /usr/local/rvm/rubies/ruby-1.9.3-p429/bin/ruby
</IfModule>

Anything special I need to do to get my environment right for this?

Much appreciated,
Guy

Internal server error
Passenger encountered the following error:

The application spawner server exited unexpectedly: Unexpected end-of-file detected.

Exception class:
PhusionPassenger::Rack::ApplicationSpawner::Error
Backtrace:

File Line Location

0 /usr/share/rubygems/gems/passenger-3.0.17/lib/phusion_passenger/rack/application_spawner.rb 135 in rescue in start&#39; 1 /usr/share/rubygems/gems/passenger-3.0.17/lib/phusion_passenger/rack/application_spawner.rb 130 instart'
2 /usr/share/rubygems/gems/passenger-3.0.17/lib/phusion_passenger/spawn_manager.rb 253 in block (2 levels) in spawn_rack_application&#39; 3 /usr/share/rubygems/gems/passenger-3.0.17/lib/phusion_passenger/abstract_server_collection.rb 132 inlookup_or_add'
4 /usr/share/rubygems/gems/passenger-3.0.17/lib/phusion_passenger/spawn_manager.rb 246 in block in spawn_rack_application&#39; 5 /usr/share/rubygems/gems/passenger-3.0.17/lib/phusion_passenger/abstract_server_collection.rb 82 inblock in synchronize'
6
> 10:in synchronize&#39; 7 /usr/share/rubygems/gems/passenger-3.0.17/lib/phusion_passenger/abstract_server_collection.rb 79 insynchronize'
8 /usr/share/rubygems/gems/passenger-3.0.17/lib/phusion_passenger/spawn_manager.rb 244 in spawn_rack_application&#39; 9 /usr/share/rubygems/gems/passenger-3.0.17/lib/phusion_passenger/spawn_manager.rb 137 inspawn_application'
10 /usr/share/rubygems/gems/passenger-3.0.17/lib/phusion_passenger/spawn_manager.rb 275 in handle_spawn_application&#39; 11 /usr/share/rubygems/gems/passenger-3.0.17/lib/phusion_passenger/abstract_server.rb 357 inserver_main_loop'
12 /usr/share/rubygems/gems/passenger-3.0.17/lib/phusion_passenger/abstract_server.rb 206 in start_synchronously&#39; 13 /usr/share/rubygems/gems/passenger-3.0.17/helper-scripts/passenger-spawn-server 102 in'

#2

> Hi! It looks like I need to be on ruby 1.9.3 for 1.2? Is that right?
>
> And my httpd/conf.d/passenger.conf files need to change to reflect that?

1.8.7, 1.9.3 and 2.0.0 are all supported, so you can stick with 1.8.

> Are you guys using rvm? I can't seem to get passenger to work with
> 1.9.3 . . .
> passenger.conf :
> LoadModule passenger_module modules/mod_passenger.so
> <IfModule mod_passenger.c>
> #PassengerRoot /usr/share/rubygems/gems/passenger-3.0.17
> #PassengerRuby /usr/bin/ruby
> PassengerRoot /usr/share/rubygems/gems/passenger-3.0.17
> PassengerRuby /usr/local/rvm/rubies/ruby-1.9.3-p429/bin/ruby
> </IfModule>

The trouble here will be passenger's compiled against the system 1.8
ruby, not your 1.9 install.

> Anything special I need to do to get my environment right for this?

If you're just wanting to develop, I'd avoid using passenger and just
run a standalone server with "script/rails server", then it'll be
listening on port 3000.

··· On 28/05/13 22:20, Guy Matz wrote:

–
Dominic Cleal
Red Hat Engineering

#3

Thanks, removing passenger helped . . . getting:
Started GET "/users/login" for 192.168.2.67 at Wed May 29 09:43:54 -0400
2013
Processing by UsersController#login as HTML
Rendered users/login.html.erb within layouts/application (37.6ms)
Operation FAILED: couldn't find file 'jquery.ui.autocomplete'
Rendered common/500.html.erb within layouts/application (18.3ms)
Completed 500 Internal Server Error in 187ms

ActionView::Template::Error (couldn't find file 'jquery.ui.autocomplete'
(in /usr/share/foreman/app/assets/stylesheets/application.scss:2)):
2: <html lang="<%= I18n.locale -%>">
3: <head>
4: <title> <%= h(yield(:title) || "Foreman") %></title>
5: <%= stylesheet_link_tag 'application' %>
6: <%= javascript_include_tag 'application' %>
7: <%= csrf_meta_tags %>
8: <%= javascript_tag "var AUTH_TOKEN =
#{form_authenticity_token.inspect};" if protect_against_forgery? %>
app/views/layouts/application.html.erb:5:in
_app_views_layouts_application_html_erb___1351484797_70150328338680&#39; app/controllers/application_controller.rb:329:ingeneric_exception'

Any ideas? I seem to be missing some javascript, but thought I had
installed all prereqs . . . I hope my contribution is worth all of the
bother I'm causing you guys! :frowning:

Thanks a lot,
Guy

··· On 05/28/2013 05:49 PM, Dominic Cleal wrote: > On 28/05/13 22:20, Guy Matz wrote: >> Hi! It looks like I need to be on ruby 1.9.3 for 1.2? Is that right? >> >> And my httpd/conf.d/passenger.conf files need to change to reflect that? > 1.8.7, 1.9.3 and 2.0.0 are all supported, so you can stick with 1.8. > >> Are you guys using rvm? I can't seem to get passenger to work with >> 1.9.3 . . . >> passenger.conf : >> LoadModule passenger_module modules/mod_passenger.so >> >> #PassengerRoot /usr/share/rubygems/gems/passenger-3.0.17 >> #PassengerRuby /usr/bin/ruby >> PassengerRoot /usr/share/rubygems/gems/passenger-3.0.17 >> PassengerRuby /usr/local/rvm/rubies/ruby-1.9.3-p429/bin/ruby >> > The trouble here will be passenger's compiled against the system 1.8 > ruby, not your 1.9 install. > >> Anything special I need to do to get my environment right for this? > If you're just wanting to develop, I'd avoid using passenger and just > run a standalone server with "script/rails server", then it'll be > listening on port 3000. >
#4

Got it. I RTFM'ed . . . rake assets:precompile seems to have resolved
the issue.

Thanks,
Guy

··· On 05/29/2013 09:47 AM, Guy Matz wrote: > Thanks, removing passenger helped . . . getting: > Started GET "/users/login" for 192.168.2.67 at Wed May 29 09:43:54 -0400 > 2013 > Processing by UsersController#login as HTML > Rendered users/login.html.erb within layouts/application (37.6ms) > Operation FAILED: couldn't find file 'jquery.ui.autocomplete' > Rendered common/500.html.erb within layouts/application (18.3ms) > Completed 500 Internal Server Error in 187ms > > ActionView::Template::Error (couldn't find file 'jquery.ui.autocomplete' > (in /usr/share/foreman/app/assets/stylesheets/application.scss:2)): > 2: > 3: > 4: <%= h(yield(:title) || "Foreman") %> > 5: <%= stylesheet_link_tag 'application' %> > 6: <%= javascript_include_tag 'application' %> > 7: <%= csrf_meta_tags %> > 8: <%= javascript_tag "var AUTH_TOKEN = > #{form_authenticity_token.inspect};" if protect_against_forgery? %> > app/views/layouts/application.html.erb:5:in > `_app_views_layouts_application_html_erb___1351484797_70150328338680' > app/controllers/application_controller.rb:329:in `generic_exception' > > Any ideas? I seem to be missing some javascript, but thought I had > installed all prereqs . . . I hope my contribution is worth all of the > bother I'm causing you guys! :-( > > Thanks a lot, > Guy > > On 05/28/2013 05:49 PM, Dominic Cleal wrote: >> On 28/05/13 22:20, Guy Matz wrote: >>> Hi! It looks like I need to be on ruby 1.9.3 for 1.2? Is that right? >>> >>> And my httpd/conf.d/passenger.conf files need to change to reflect that? >> 1.8.7, 1.9.3 and 2.0.0 are all supported, so you can stick with 1.8. >> >>> Are you guys using rvm? I can't seem to get passenger to work with >>> 1.9.3 . . . >>> passenger.conf : >>> LoadModule passenger_module modules/mod_passenger.so >>> >>> #PassengerRoot /usr/share/rubygems/gems/passenger-3.0.17 >>> #PassengerRuby /usr/bin/ruby >>> PassengerRoot /usr/share/rubygems/gems/passenger-3.0.17 >>> PassengerRuby /usr/local/rvm/rubies/ruby-1.9.3-p429/bin/ruby >>> >> The trouble here will be passenger's compiled against the system 1.8 >> ruby, not your 1.9 install. >> >>> Anything special I need to do to get my environment right for this? >> If you're just wanting to develop, I'd avoid using passenger and just >> run a standalone server with "script/rails server", then it'll be >> listening on port 3000. >>
#5

> Got it. I RTFM'ed . . . rake assets:precompile seems to have resolved
> the issue.
>

if you are running from git / develop mode, you won't need to compile the
assets…

if you just hacking your way around existing packages, I would recomend
switch to git and using bundler?

Ohad

··· On Wed, May 29, 2013 at 5:08 PM, Guy Matz wrote:

Thanks,
Guy

On 05/29/2013 09:47 AM, Guy Matz wrote:

Thanks, removing passenger helped . . . getting:
Started GET “/users/login” for 192.168.2.67 at Wed May 29 09:43:54 -0400
2013
Processing by UsersController#login as HTML
Rendered users/login.html.erb within layouts/application (37.6ms)
Operation FAILED: couldn’t find file 'jquery.ui.autocomplete’
Rendered common/500.html.erb within layouts/application (18.3ms)
Completed 500 Internal Server Error in 187ms

ActionView::Template::Error (couldn’t find file ‘jquery.ui.autocomplete’
(in /usr/share/foreman/app/assets/stylesheets/application.scss:2)):
2:
3:
4: <%= h(yield(:title) || “Foreman”) %>
5: <%= stylesheet_link_tag ‘application’ %>
6: <%= javascript_include_tag ‘application’ %>
7: <%= csrf_meta_tags %>
8: <%= javascript_tag “var AUTH_TOKEN =
#{form_authenticity_token.inspect};” if protect_against_forgery? %>
app/views/layouts/application.html.erb:5:in
_app_views_layouts_application_html_erb___1351484797_70150328338680' app/controllers/application_controller.rb:329:ingeneric_exception’

Any ideas? I seem to be missing some javascript, but thought I had
installed all prereqs . . . I hope my contribution is worth all of the
bother I’m causing you guys! :frowning:

Thanks a lot,
Guy

On 05/28/2013 05:49 PM, Dominic Cleal wrote:

On 28/05/13 22:20, Guy Matz wrote:

Hi! It looks like I need to be on ruby 1.9.3 for 1.2? Is that right?

And my httpd/conf.d/passenger.conf files need to change to reflect
that?

1.8.7, 1.9.3 and 2.0.0 are all supported, so you can stick with 1.8.

Are you guys using rvm? I can’t seem to get passenger to work with
1.9.3 . . .
passenger.conf :
LoadModule passenger_module modules/mod_passenger.so

#PassengerRoot /usr/share/rubygems/gems/passenger-3.0.17
#PassengerRuby /usr/bin/ruby
PassengerRoot /usr/share/rubygems/gems/passenger-3.0.17
PassengerRuby /usr/local/rvm/rubies/ruby-1.9.3-p429/bin/ruby

The trouble here will be passenger’s compiled against the system 1.8
ruby, not your 1.9 install.

Anything special I need to do to get my environment right for this?
If you’re just wanting to develop, I’d avoid using passenger and just
run a standalone server with “script/rails server”, then it’ll be
listening on port 3000.

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.