I try to replace Apache by a lighter server: lighttpd. The installation is with no problem at all. The configuration by default works well with files html. (It works). But I cann't configure lighttpd to work with php. I read that it is necessary to install php-cgi with all its dependences. This is made. I also found that it is necessary to validate: include "conf.d/fastcgi.conf" in modules.conf. But the file fastcgi.conf does not exist.
Any ideas guys ?
CC: (none) => fundawang, guillomovitch, luigiwalser
Our packages lacks a large number of sample config files, I just added them. I also added a small php configuration file, stolen from Fedora. Please test new 1.4.30-3.mga2 release.
I had already tried with Fedora's file. I have just redone the try. It does not work. On the other hand, on the forum of Mageia, I just found the good solution: a link to http://www.cyberciti.biz/tips/lighttpd-php-fastcgi-configuration.html With this configuration, it is OK.
Well, if the only problem was "missing proper configuration directives", that's not really a packaging problem, and the issue can be closed.
Status: NEW => ASSIGNED
I would like not to close the report. I found so bad solutions on the Internet that I think: it would be useful to create a fastcgi.conf file correctly adapted to Mageia.
There is such a configuration file already, the upstream one. I have no clue about how it is adapted, sure, but I'd rather avoid adding yet another piece of personal suggestions here, especially as I have no expertise of lighttpd at all...
Created attachment 1779 [details] Proposed fastcgi.conf file Yes, I understand. I have just ended my tries and I propose, in appendix, a very simple file which works. In the modules.conf file, the user does not have more than has to validate the line include "conf.d/fastcgi.conf"
Changing status back to assigned, unless you want it Guillaume, in which case we should change the assignee :)
Status: ASSIGNED => NEWCC: (none) => remco
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
2 months later, no reply, closing as old Feel free to reopen if needed and tell in which fully updated Mageia version(s) you still have this issue
Status: NEW => RESOLVEDCC: (none) => marja11Resolution: (none) => OLD