Ticket #6224 (closed enhancement: fixed)
Opened 4 years ago
Last modified 3 years ago
Add support for FCGI to tracd (standalone.py)
| Reported by: | josh@… | Owned by: | mgood |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.12 |
| Component: | web frontend/tracd | Version: | |
| Severity: | normal | Keywords: | patch |
| Cc: | mgood | ||
| Release Notes: | |||
| API 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
Change History
Changed 4 years ago by josh@…
- Attachment standalone_fcgi.diff added
comment:1 Changed 3 years ago by rblank
- Keywords patch added
- Milestone set to 1.0
- Owner jonas deleted
I'm not competent to evaluate the validity of this change, but the patch seems simple enough.
comment:2 Changed 3 years ago by cboos
- Cc mgood added
Never used fcgi myself either, but that part of the code was managed by mgood, CC'ing him.
comment:3 Changed 3 years ago by mgood
- Milestone changed from 1.0 to 0.12
- Resolution set to fixed
- Status changed from new to closed
LGTM. Applied in r7686.
comment:4 Changed 3 years ago by rblank
- Owner set to mgood
comment:5 Changed 3 years ago by sergej.spb@…
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.