#10435 closed enhancement (fixed)
FastCGI scripts are not synchronized
| Reported by: | Owned by: | Remy Blank | |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.0 |
| Component: | general | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | osimons | Branch: | |
| Release Notes: |
Moved old |
||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
FastCGI script available from tags/trac-0.12.2/trac/admin/templates/deploy_trac.fcgi is different from tags/trac-0.12.2/cgi-bin/trac.fcgi
Attachments (0)
Change History (7)
comment:1 by , 12 years ago
| Milestone: | → 0.13 |
|---|---|
| Owner: | set to |
| Type: | defect → enhancement |
follow-up: 3 comment:2 by , 12 years ago
From the other side I remember it was hard to find information where to get scripts to run Trac in FastCGI or WSGI mode.
But even generated scripts won't help much when you're running Trac from under Nginx (should be very popular setup, BTW). It uses different script (based on cgi-bin) patched to use socket communication.
And for virtualenv you need to modify scripts as well.
comment:3 by , 12 years ago
Replying to anatoly techtonik <techtonik@…>:
But even generated scripts won't help much when you're running Trac from under Nginx (should be very popular setup, BTW). It uses different script (based on
cgi-bin) patched to use socket communication.And for
virtualenvyou need to modify scripts as well.
That's true. The generated scripts tend to serve as a basis and often require installation-specific changes, and it would be difficult to make them generic enough for everyone. We could improve them somewhat by adding more examples and documentation in the scripts themselves, for example by mentioning PYTHON_EGG_CACHE and the lines for activating a virtualenv. But they will probably always require manual editing.
follow-up: 5 comment:4 by , 12 years ago
| Cc: | added |
|---|---|
| Description: | modified (diff) |
The fact that these scripts don't contain any environment variable modifications makes them useful - it means you can pass in whatever you want/need from the outside without it being modified by hard-coded values from deploy. The scripts do work fine as long as they get the data they need.
However, to avoid confusion perhaps move them to contrib/cgi-bin instead?
comment:5 by , 12 years ago
Replying to osimons:
However, to avoid confusion perhaps move them to
contrib/cgi-bininstead?
Makes sense.
comment:7 by , 12 years ago
| Release Notes: | modified (diff) |
|---|
Funny, I never noticed that we had these files in
cgi-bin. We should remove thecgi-bindirectory, those files are 5 years old, and have probably been superseded by the files generated bytrac-admin $ENV deploy.