WikiStart¶

New Releases¶

• version:"1.6.6" 2025-03-01
• version:"1.6.5" 2022-12-21
• version:"1.6.4" 2014-06-05 (fixed bugs)
• version:"1.6.3" 2009-09-23 (fixed bugs)
• version:"1.6.2" 2009-04-18 (fixed bugs)
• version:"1.6.1" 2009-03-29 (fixed bugs)
• version:"1.6.0" 2009-02-28 (fixed bugs)

Why you should use spawn-fcgi instead of something else¶

• Privilege separation without needing a suid-binary or running a server as root.
• Protect (unix) socket - only the webserver can connect to your backend (especially php can be vulnerable if untrusted users can connect)
• You can restart your web server and the FastCGI applications without restarting the others.
• You can run them in different chroot()s.
• Running your FastCGI applications doesn’t depend on the web server you are running, which allows for easier testing of/migration to other web servers.
• Actually you don't need spawn-fcgi if you have systemd - see systemd

Building¶

• Build from normal releases/snapshots
• Build from git

Usage¶

• Basic Ideas
• Example run scripts for daemontools or runit: source:/trunk/doc/

Known issues¶

• Windows: doesn't work with "native" (i.e. not cygwin) binaries.
  See http://redmine.lighttpd.net/boards/2/topics/686 (http://redmine.lighttpd.net/attachments/727/spawn-fcgi-win32.c)

Pages in lighttpd wiki¶

• Example:fastcgiCentosInitScript
• ScriptsUbuntu
• HowToSetupFastCgiIndividualPermissions
• HowToSetupFastCgiIndividualPermissionsInitScript
• HowToRestartLocalBackendWithoutDowntime
• HowtoSpeedUpStatWithFastcgi
• Docs:ModFastCGI

Development¶

• Release-Procedure