Ruby on Rails Saturday, September 29, 2012

2012/9/29 Mandeep Kaur <>:

> Then how can I access site without port. Please give some idea how can
> I do this?

When your Apache is configured to listen on port 80 AND apache is
configured to serve a certain VirtualHost via Passenger, THEN no port
in the URL is needed.

The documentation of passenger itself is very straight forward. The
only mistakes you can make is to "name" the VirtualHost wrong, set the
Passenger pathes wrong or put the DocumentRoot into a wrong directory.
If you have none of this wrong, everything should work.

Hint 1: All I say now is for PRODUCTION!
Hint 2: ServerName has to be the domain you bought, or any subdomain
that is resolved to the same IP-Address.
Hint 3: RailsEnv shall be production
Hint 4: PassengerRoot and PassengerRuby should point to the root-dirs
in which the appropriate binaries are located.
Hint 5: After changing apache config don't forget to restart it, can
take hours to find that damn mistake, been there, done that…
Hint 6: Remember to touch that file passenger needs to recognize the
updated app and restart it, after you changed something, also an error
that will eat hours of your life…
Hint 7: Last but not least: Learn to use a deploy-tool like Capistrano
or Vlad, it will make many things easier and do things automatically
that I personally would forget with every deploy (see Hint 5 and 6 :)

When none of these Hints help you, you should learn how to find the
various logs apache provides, there will be questions about their
contents then.

You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit

No comments:

Post a Comment