Edgewall Software
Modify

Opened 9 years ago

Closed 9 years ago

Last modified 8 years ago

#10435 closed enhancement (fixed)

FastCGI scripts are not synchronized

Reported by: anatoly techtonik <techtonik@…> Owned by: Remy Blank
Priority: normal Milestone: 1.0
Component: general Version:
Severity: normal Keywords:
Cc: osimons Branch:
Release Notes:

Moved old cgi-bin/ script to contrib/cgi-bin. The script might still be useful when trac-admin <env> deploy is not wanted.

API Changes:
Internal Changes:

Description (last modified by osimons)

Attachments (0)

Change History (7)

comment:1 by Remy Blank, 9 years ago

Milestone: 0.13
Owner: set to Remy Blank
Type: defectenhancement

Funny, I never noticed that we had these files in cgi-bin. We should remove the cgi-bin directory, those files are 5 years old, and have probably been superseded by the files generated by trac-admin $ENV deploy.

comment:2 by anatoly techtonik <techtonik@…>, 9 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.

in reply to:  2 comment:3 by Remy Blank, 9 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 virtualenv you 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.

comment:4 by osimons, 9 years ago

Cc: osimons 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?

in reply to:  4 comment:5 by Remy Blank, 9 years ago

Replying to osimons:

However, to avoid confusion perhaps move them to contrib/cgi-bin instead?

Makes sense.

comment:6 by Remy Blank, 9 years ago

Resolution: fixed
Status: newclosed

Done in [10974].

comment:7 by Christian Boos, 8 years ago

Release Notes: modified (diff)

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Remy Blank.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Remy Blank to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.