Opened 6 years ago

Closed 2 years ago

#11694 closed Cleanup/optimization (wontfix)

lighttpd fastcgi documentation not working

Reported by: buggerone@… Owned by:
Component: Documentation Version: 1.1
Severity: Normal Keywords: deployment, lighttpd
Cc: onelson@…, django@… Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

The admin part is not accessible with the configuration described.
With default configuration, django links to /mysite.fcgi/admin wich is rewrited (by lighttpd) as /mysite.fcgi/mysite.fcgi/admin

the setting FORCE_SCRIPT_NAME needs to be set to "". This should be described in documentation.

Change History (9)

comment:1 follow-up: Changed 6 years ago by aszlig

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

Hm, this whole FORCE_SCRIPT_NAME thingy was always required before and is documented at the bottom of the deployment documentation.

Maybe it's a good idea to avoid FORCE_SCRIPT_NAME by changing the documentation example to something like:

server.modules += (
        "mod_alias",
        "mod_fastcgi",
)

server.document-root = "/home/user/public_html"

fastcgi.server = (
    "/" => ((
        "socket" => "/home/user/mysite.sock",
        "check-local" => "disable",
        "fix-root-scriptname" => "enable",
    )),
)

$HTTP["url"] =~ "/(?:media(?:$|/)|favicon\.ico$|... whatever you want to serve directly ...)" {
    fastcgi.server = ()
    alias.url = (
        "/media"  => "/home/user/django/contrib/admin/media/",
    )
}

comment:2 Changed 5 years ago by russellm

  • Triage Stage changed from Unreviewed to Accepted

Sounds like there might be something going on here that should be improved, but it's not just a matter of updating the example. We need someone who knows what they are doing to do a full review of the fastcgi docs.

comment:3 Changed 5 years ago by russellm

#11754 was a duplicate that indicated some other problems with the fastcgi docs.

comment:4 Changed 5 years ago by gabrielhurley

  • Keywords deployment added
  • Owner changed from nobody to gabrielhurley
  • Status changed from new to assigned

I've got a reasonable knowledge of lighttpd + fcgi (all my live sites are currently deployed on it). I'll review these docs along with the variety of other fcgi-related docs tickets that are currently accepted.

comment:5 Changed 5 years ago by onelson@…

  • Cc onelson@… added

CC'ing myself so I remember to add something regarding init.d scripts for site daemons. Had issues with permissions using unix sockets (unless managed via services). I'm imagining socket is preferred for those running the fcgi process on the same host as the web server.

comment:6 Changed 4 years ago by gabrielhurley

  • Owner gabrielhurley deleted

comment:7 Changed 4 years ago by baumer1122

  • Severity set to Normal
  • Type set to Cleanup/optimization

comment:8 in reply to: ↑ 1 Changed 4 years ago by jedie

  • Cc django@… added
  • Easy pickings unset
  • Keywords lighttpd added
  • UI/UX unset

Replying to aszlig:

Hm, this whole FORCE_SCRIPT_NAME thingy was always required before and is documented at the bottom of the deployment documentation.

Yes, it is documented, but at the bottom of the page. And that's why i didn't see it :(
IMHO it's a good idea to put a info box in the section of lighttpd setup, directly under the lighttpd config example.

The example from aszlig doesn't work good with multiple sites, isn't it?

comment:9 Changed 2 years ago by timo

  • Resolution set to wontfix
  • Status changed from assigned to closed

FastCGI is being deprecated.

Note: See TracTickets for help on using tickets.
Back to Top