[ previous ] [ next ] [ threads ]
 
 From:  "Iedema, Michael" <iedemam at pluto dot dsu dot edu>
 To:  "'Michael Mee '" <mm2001 at pobox dot com>
 Cc:  "'m0n0wall at lists dot m0n0 dot ch'" <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] m0n0wall php dev environment tips?
 Date:  Sun, 15 Jun 2003 22:24:37 -0500
I don't know if anyone has responded to this yet.  I was out of town, and my
mailbox was over its size limit.... mail==halted


Anyway, the simplest way I can imagine would be to:

1. Develop the page
2. Enable firmware upload utility (turn the ftp on)
3. Ftp the page up.
4. Open a browser and head to http://m0n0wall-ip/exec.php
5. Execute the folowing cp /ftmp/* /usr/local/www
5. Type in the address of that page to try out your experiment.


I've used this method messing around with my own failed php attempts.  It
resets itself once the machine has been reset so you are at no loss.  Once
the page works, submit your mastery to Mr. Kasper.  I'm sure it would be
appreciated.

Hope this helps,
--Michael





-----Original Message-----
From: Michael Mee
To: m0n0wall at lists dot m0n0 dot ch
Sent: 6/13/03 2:05 PM
Subject: [m0n0wall] m0n0wall php dev environment tips?

I'd like to add some php features to m0n0wall (more stats, static DHCP
assignments) and am wondering about the simplest php dev environment.

Ideally I'd like to use a freeBSD machine and simply run the php pages
on
the machine and have it mess with the config files etc., but without
messing
up the main machine. It *seems* like a good use for chroot, but I
honestly
don't know enough about it to know if I'm on the right track. I'm happy
to
track down the details but a quick 'yes its straight-forward' or 'it
might
work, but will be tricky, how about XXX instead' could save me a lot of
time.

Any/all advice appreciated. I'll reciprocate with the steps I take to
get it
working. (I.e., a 'hacking m0n0wall lite' version).

Fwiw, I have read http://m0n0.ch/wall/hack/ and it was very useful, but
since I'm only interested in making php changes and additions (at this
stage), I'd like to save some steps and time in the code-build-test
cycle
and only build an image occaisionally when I've got new php debugged.
(I'm
also limited by only having one Soekris box which is in constant use, so
I
want to keep its reboots to a minimum - currently I ftp files to the box
and
then use http://<myn0n0wall>/exec.php to copy them to the right place
when I
have something I want to try.)

cheers, michael


---------------------------------------------------------------------
To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch