#6224 closed enhancement (fixed)
Add support for FCGI to tracd (standalone.py)
Reported by: | Owned by: | Matthew Good | |
---|---|---|---|
Priority: | normal | Milestone: | 0.12 |
Component: | web frontend/tracd | Version: | |
Severity: | normal | Keywords: | patch |
Cc: | Matthew Good | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
By adding fcgi as an option to flup (http, scgi, ajp are already there), trac can easily be used with web servers that don't support spawning an fcgi process (such as nginx) but will communicate with an already running fcgi server. See attached diff.
Attachments (1)
Change History (6)
by , 17 years ago
Attachment: | standalone_fcgi.diff added |
---|
comment:1 by , 16 years ago
Keywords: | patch added |
---|---|
Milestone: | → 1.0 |
Owner: | removed |
I'm not competent to evaluate the validity of this change, but the patch seems simple enough.
comment:2 by , 16 years ago
Cc: | added |
---|
Never used fcgi myself either, but that part of the code was managed by mgood, CC'ing him.
comment:3 by , 16 years ago
Milestone: | 1.0 → 0.12 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
LGTM. Applied in r7686.
comment:4 by , 16 years ago
Owner: | set to |
---|
comment:5 by , 16 years ago
There is some problem when you try to pass for example —hostname=/some/path/fcgi.sock with —protocol=fcgi and without any —port value. I've got an error: socket.gaierror: (-2, 'Name or service not known'). Problem was resolved by replacing on line 240 server_address with options.hostname.
I suspect that such solution isn't the best, but it works for me.
Diff to add FCGI server capability to tracd.