Puppy: Web Server Edition

[Bappy]

yea, phpinfo() seems fine and I hadn't set a root password although I think I have now. (it said 0 rows affected??)

I haven't touched the httpd.conf file at all that I remember.

[Bappy]

well it works now.

just a really slow server - had to increase the cgi script timeout.

Now the next thing in my list...

has anyone compiled PDO's MySQL driver for php? also what php caching options are there available? APC? eAccelerator?

I don't have a development machine on which to compile stuff myself

[ottod]

ftp.servage.net is kind of "empty" right now.
I am interested in the version for Puppy 4.1.2 released Dic 30 2008 but because the post does not mention its name (only its location at servage.net) I cannot search for a copy somewhere else.

[raffy]

Download the sfs here
http://minipc.org/lamp/growler-amp_412.sfs

[scsijon]

Check out the wiki entry

http://www.puppylinux.org/wiki/archives ... h-hiawatha

There are real advantages to the hiawatha web-server already bundled with puppy compared to apache.

This link doesn't seem to go anywhere any more , just a 404-file not found

any alternatives, please

this thread will save me "reinventing"

thanks

[growler]

Yes the old wiki was ditched - I took the liberty of setting up outside the puppy web-sites which do get updated regularly.

http://www.weberp.org/PuppyLinux

[scsijon]

thanks for that

[ken geometrics]

I was looking today and it dawned on me that Puppy could very well make a nice lightweight web server for personal use. (Testing server or small personal web host). So, using 4.1.2 as a base, I'm going to start trying to put together some things, including compiling and packaging php, MySQL, and Apache into pets. (Won't be small, unfortunately). Anyone have any other suggestions/comments/observations for this?

You can make the pages all dangle off a symbolic link. This way the CD doesn't need to have them on it. The save file and the pages can all live on the same memory stick. This way, no matter how much data there is the RAM space and the CD don't get full.

[scsijon]

my primary consideration is that everything of a "fixed" nature would live on a CD, everything of a "changeable" nature would be live in ram and be backloaded into a memory stick by the system on a predetermined time.

alternately there could be two partitions on the memory stick (I take it this can be done), one having the system and fixed parts and be permanently set as RO only when in a "running state", the second partition being for a live backup of the "changeable" parts only, keeping earlier versions, say on a ?hourly basis in case of corruptions, etc., and being set as write only by system.

Or something like that.

scsijon

ps i've ended up going browserpuppy.com 's webserver, see my topic in puppy projects for what i'm up too. I'll keep it up to date, so please don't pm me.