set up a website 2

[kurie]

hi all
i have got php files(which make up a website) and i have been asked to help correct some errors on the site, i need to setup the website, i have got dreamweaver on my machine to edit the php files, i havent used PHP before(just helping a friend), how do i go abt setting a site using these files

Thanks

 

[feherke]

Hi

[ul]
[li]install a web server[/li]
[li]install PHP[/li]
[li]configure the web server to use PHP[/li]
[li]copy the site's source code into webserver's data directory[/li]
[/ul]
This is a generic answer for your generic question.

If not satisfied, give us some details. At least specify the operating system. Or tell us what you have so far.

Feherke.

http://rootshell.be/~feherke/

 

[kurie]

i think thats what i want. thanks
can i run the app without configuring the webserver like debug in .net

 

[feherke]

Hi

I know nothing about .net, but supposedly you are talking about some development environment, which may have its own webserver embedded.

For debugging see Aptana. But of course the configuring is not optional.

If you aim to skip the configuration, you can try XAMPP ( or something similar listed in List of AMP packages ).

Feherke.

http://rootshell.be/~feherke/

 

[jpadie]

this is a penetrating glance into the glaringly obvious but ...

the usefulness of xDebug or ZendDebug (etc) for debugging stateless php applications depends almost entirely on how the application is designed. I find that the more modular the design of my application (lots of separate objects appropriately interrelated) the less useful IDE debuggers are.

I find xDebug most useful when i use a despatch methodology and then have separate pages/functions handling response. In such a case the php process has less than a 1000 lines or so of code parsed at any one time. this is only credible for very simple applications however.

By way of contrast, I am in the process of coding a very large plugin for wordPress. If i use a debugger on this it can take 15 minutes of stepthrough before i have even got to the point in the code I am interested in...

sometimes, I use debuggers with breakpoints but I have found that their behaviour is not always consistent.

So I always find myself falling back on the old faithful of footprinting. usually with a helper function to store the output in the file system. the advent of debug_backtrace() is also a huge bonus.

 

[feherke]

Hi

Thanks for sharing that, jpadie. I found it interesting.

Feherke.

http://rootshell.be/~feherke/