No luck with index.php - the browser just tries to download it :)
I have attached the modified index.html file to show what I've tested
with, and what does not work. It seems so simple... how can it not
work!?
Btw, not really worried about speed/scaling. Just working (without
needing Cherokee-admin).
Jeremy
From: Chad Smith [mailto:[email protected]]
Sent: Wednesday, March 30, 2011 6:52 AM
To: Jeremy Greene
Cc: [email protected]
Subject: Re: [Cherokee] php question (really having to do with embedded
operation)
Jeremy,
I personally use PHP-FPM. I noticed that it gives you a lot more of a
performance boost than the traditional php-cgi. Plus it's a lot more
configurable. My API that I'm running Cherokee/PHP-FPM on is currently
doing about 1.2 million successful API requests a week. I would suggest
looking into using that as it's more manageable as I said. It's
configured to listen on 127.0.0.1:9000 which is fine. Then
Cherokee-admin will notice that there's PHP installed and find the
interpreter. How? That's for one of the other Cherokee fanatics to
discuss but all I know is that it found it and uses it.
Check out PHP-FPM : http://php-fpm.org/
Take care,
Chad
On Wed, Mar 30, 2011 at 6:46 AM, Jeremy Greene <[email protected]>
wrote:
Hi Chad,
Thanks for the help. I will try an index.php (instead of index.html).
As to the docs on the Cherokee web site for php: run Cherokee-adim. That
doesn't work for me.
I really could use a basic recipe on how to do this without
Cherokee-admin
Jeremy
From: Chad Smith [mailto:[email protected]]
Sent: Tuesday, March 29, 2011 10:18 PM
To: Jeremy Greene
Cc: [email protected]
Subject: Re: [Cherokee] php question (really having to do with embedded
operation)
"index.html" that's the part that concerns me. Add in an index.php
instead of index.html, you also have to tell Cherokee that you want to
process index.php as a document root. I'm sure one of the other fine
folks on this list will be happy to show you how to add that as a
document index.
Also did you add in the PHP CGI into your Vhost? That's another part
that you need to do, if not then Cherokee has no idea that it should be
sending stuff to PHP.
Just some things to get you started, also take a look at the
documentation. I believe there's a writeup on how to get PHP configured
with Cherokee.
Thanks,
Chad Smith
http://theeasyapi.com
On Tue, Mar 29, 2011 at 9:29 PM, Jeremy Greene <[email protected]>
wrote:
Hi again,
I still haven't gotten the server to process php correctly.
(added <p><?php print 'Hello World'; ?></p> to the sample
index.html file)
Below there is output from Cherokee -i. And php-cgi -v. And a run of the
server.
I can't run the admin server - can't get python to run on the target.
Should it just work, or do I need to make changes to Cherokee.conf?
If changes are needed to the conf file, can someone tell me what they
are?!
Note the funny output in the builtin plugins list - is this an
indication of a problem?
For the truly dedicated, included the config.log file :)
Thanks for any help!!
Jeremy
=========================
[email protected]:~ <mailto:[email protected]:%7E> #
/home/jgreene/cherokee_test/sbin/cherokee -i
Compilation
Version: 1.2.2
Compiled on: Mar 29 2011 17:09:19
Arguments to configure: '--host=mipsel-linux' '--enable-static'
'--enable-shared=no' '--enable-static-module=all' '--enable-trace'
'--prefix=/home/jgreene/cherokee_test' '--disable-tls'
'--with-libssl=no' '--with-php=/home/jgreene/php/bin'
'host_alias=mipsel-linux' 'CC=mipsel-linux-gcc'
'CPPFLAGS=-D__NO_MATH_INLINES -D__NO_STRING_INLINES'
Installation
Deps dir: /home/jgreene/cherokee_test/share/cherokee/deps
Data dir: /home/jgreene/cherokee_test/share/cherokee
Icons dir: /home/jgreene/cherokee_test/share/cherokee/icons
Themes dir: /home/jgreene/cherokee_test/share/cherokee/themes
Plug-in dir: /home/jgreene/cherokee_test/lib/cherokee
Temporal dir: /tmp
Plug-ins
Built-in: or and cgi not rrd ssi tls bind drop fcgi file from gzip ncsa
scgi v_or admin plain proxy redir uwsgi common custom evhost exists
header method rehost deflate dirlist ip_hash request url_arg authlist
combined error_nn failover fullpath htdigest htpasswd wildcard directory
empty_gif target_ip extensions post_track render_rrd error_redir
post_report round_robin secdownload server_info custom_error
Support
IPv6: yes
Pthreads: yes
Tracing: yes
sendfile(): yes
syslog(): yes
Polling methods: epoll poll select
[email protected]:~ <mailto:[email protected]:%7E> #
/home/jgreene/php/bin/php-cgi -v
PHP 5.3.6 (cgi-fcgi) (built: Mar 29 2011 12:38:53)
Copyright (c) 1997-2011 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2011 Zend Technologies
[email protected]:~ <mailto:[email protected]:%7E> #
[email protected]:~ <mailto:[email protected]:%7E> #
/home/jgreene/cherokee_test/sbin/cherokee
[29/03/2011 23:25:51.565] (warning) socket.c:436 - IPv6 support is
disabled.
Configuring for IPv4 support only. | The issue seems to be related
to your system.
Cherokee Web Server 1.2.2 (Mar 29 2011): Listening on port ALL:80, TLS
disabled, IPv6 enabled, using epoll, 4096 fds system limit, max. 2041
connections, 5 threads, 408 connections per thread, standard scheduling
policy
From: Jeremy Greene
Sent: Monday, March 28, 2011 5:45 PM
To: '[email protected]'
Subject: php question
Hi,
I have downloaded Cherokee and cross-compiled it for a mips-based
embedded system running a stripped-down linux. It is running on that
system, but php is not enabled (the default page is served fine). I
thought enabling php would be an easy step.
Well, first, running the Cherokee admin server.... I gave up on that
after trying to get python to run on my embedded system for a few hours.
I have no idea how this is intended to work... clearly requiring python
on an embedded system isn't reasonable. I tried to do it in a temp way
with nfs mounts on a development system... but just couldn't get there.
So I decided to go the manual conf route.
First step... the php on the target system does not have fastcgi
support.
Ok, download the latest php... wow, wow, wow. Embedded and php really
aren't good in the same sentence. Disabling things like XML support...
well, not easy (seems like an error in the configure script).
Anyway, I'm going through the process of nixing things like XML,
simplXML, PEAR... and thought I'd just check in with others to see if
I'm just trying to fit a square peg into a round hole. I guess the real
question is: even though Cherokee may be suitable for an embedded
system, is PHP not?!
Thanks in advance for any guidance!!
Jeremy
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
Title: Cherokee Test Page
This page is used to test the proper operation of the Cherokee Web Server after it has been installed. If you can read this page, it means that the Cherokee Web Server installed at this site is working properly.
Note: If you see this page after uploading site content you probably have not replaced the index.html file.
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
