Ruby on Rails | Screencasts | Download | Documentation | Weblog | Community | Source

Ticket #5004 (new enhancement)

Opened 2 years ago

Last modified 2 years ago

[PATCH] Pass location of lighttpd binary and modules to lighttpd.rb

Reported by: elliot@townx.org Assigned to: David
Priority: normal Milestone: 1.2.7
Component: Railties Version: 1.1.1
Severity: minor Keywords:
Cc:

Description

It's useful to be able to pass the location of the lighttpd binary and modules to the lighttpd.rb script, for cases where lighttpd is installed in a non-standard location not on the path, or where multiple versions are available on the same system. This patch adds two options for passing these options to the script: 

'-l', "--lighttpd_modules=path", 'Path to lighttpd modules (e.g. /opt/lightty/lib)'
'-e', "--lighttpd=path", 'Path to lighttpd executable (e.g. /opt/lightty/bin)

NB the server.rb script ignores these options unless "script/server lighttpd" is specified explicitly.

Attachments

lighttpd.rb.diff (2.3 kB) - added by elliot@townx.org on 05/08/06 10:49:38.
Patch to allow passing of non-standard lighttpd locations to lighttpd.rb script

Change History

05/08/06 10:49:38 changed by elliot@townx.org

  • attachment lighttpd.rb.diff added.

Patch to allow passing of non-standard lighttpd locations to lighttpd.rb script

05/08/06 16:36:19 changed by bitsweat

  • type changed from defect to enhancement.

Is export PATH="/opt/lighty/bin:${PATH}" insufficient, or do you prefer being explicit?

Also, script/server -e already sets the Rails environment when using webrick.

05/08/06 18:35:05 changed by elliot@townx.org

I think it helps to be explicit, and can prevent confusion in cases where multiple Lighttpd instances are on the server, or if you are packaging an application with Lighttpd and want to ensure the correct binary is used when it's moved to a different machine.

Yes, I'd missed -e (a bit of an oversight). I'm not precious about the names of the options, just that they are available.