permission headaches (ooh... my head)

[Anon]

hmm...

i've been developing a site on a standalone machine for a while now, with win95, PWS & PHP4. the site creates .html pages using PHP scripts every so often (say once a day), at the minute these PHP scripts are run over the server (as opposed to compiling PHP as a standalone scripting thingy) but i've hit a problem now i've put the site on the proper server where i dont have the same privelages.

the site now sits on an Linux/Apache box which i can telnet into over a unix network, but the only way i can get my PHP scripts to write html files on the server when accessing over the web is to set the permissions to 777, not exactly ideal as other people sharing the network i'm on can then just wonder into my htdocs directory and delete/edit/move my files. if i set them to the usual 755, i just get complaints about not having the right permissions... is there any obvious solution to this that i'm missing?

i've considered compiling PHP as a binary and using this on the server to do the generating of files, but i do like the idea of a password protected area in my site where the html file generation can be done...

thanks in advance

dom
🙂

[Anon]

There are two settings in apache, one called User and another called Group (generally at the beginning of the configuration, and by default they are both set to nobody). Either create a user for apache to run as and chown all of your htdocs files and directories to that user, or leave as is and chown to nobody (but then you won't have access). If you don't understand how ownership and group permissions work, consult your local unix guru before continuing please.

Chris King