I have problems with the configuration of a server cherokee with we2py.
I follow the Cherokee with FastCGI manual from:
http://www.web2py.com/books/default/chapter/29/13.
1) create the file /var/web2py/startweb2py.sh and set as executable
with this content:
#!/bin/sh
sudo -u www-data python /var/web2py/fcgihandler.fcgi &
2) enter in cherokee-admin al port 9090 and config sources with:
Nick: web2py
Connection: /tmp/fcgi.sock
Interpreter: /var/web2py/startweb2py.sh
3) edit vserver default handler with fastcgi and FastCGI Specific set
round robin and Assign Information Sources to web2py source
before start cherokee server, execute startweb2py.sh and enter to mi
ip in the webbrowser al show the startpage from cherokee, i use mi
ip/web2py and show error 404.
what is wrong?
I also try lighttp but the configuration not was successfull.
PD: i cant use apache
Solved my self, thanks
2012/1/27 Roberto Perdomo <rober...@gmail.com>:
The essence is that you create an scgi handler in cherokee. You set
cherokee to use scgihandler.py inside the root of web2py as startup
process in that same scgihandler. Then you are done.
Else use nginx it is excellent see this:
http://www.web2pyslices.com/slices/take_slice/143
There you see a simplified setup. In production I suggest to use
daemontools to manage the scgihandler process: works like a charm.
mic
p.s. ;-) good thing you can't use apache+wsgi with cherokee+scgi my
system is able to handle 5 times more requests (with session.forget())
;-)
2012/1/27 Roberto Perdomo <rober...@gmail.com>:
Thank for you suggest. The next monday i try.
Today with cherokee and fastcgi the welcome app work fine, but only show the index, and with other apps is the same problem.
> I have problems with the configuration of a server cherokee with
> we2py.
Have you considered Cherokee + uWSGI?
Sincerely,
Gour
--
In this endeavor there is no loss or diminution,
and a little advancement on this path can protect
one from the most dangerous type of fear.
http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810