Building a Web Site is a complicated task because you have many pieces that have to be put into place. It took me a long time to put everything together and know how it all works together. To put an apache web server together with PHP, Perl, and MySQL is a large feat. You will have to learn at least a little about the following:
You’re operating system like UNIX, LINUX, or Windows and how it handles security (e.g. permission).
Your web server and how to configure it. Both IIS and apache have to be configure to know where the cgi-bin is, where the home directory is, what other directories like PHP, etc have execute permission, how to associate an extension with the executable that can run it, etc.
If you want anything more than static HTML you need to know a scripting language like Perl, PHP, Visual Basic, C++, etc.
You need to know how to install your scripting language and to configure your web server to use it. (e.g. the apache httpd.conf).
You probably need to know something about you firewall application.
Be sure and learn how to backup everything relevant to your Web Site.
If you want to use a database you need to know how to create SQL command and how to setup the Web Server to interface with it.
You have multiple layers and I’ve found it usually best to keep them separate. You have the Web Server layer that hangs out in memory to intercept any request coming over an assigned port. It creates threads to serve up Web pages. You have your business logic layer (e.g. the cgi-bin directory). There should probably be nothing in it but executables and perhaps some text files that the executable needs. If you have a perl script in your web’s home directory for example, the browse might try to display it as opposed to executing it. Some Languages allow you to embed script right into the HTML, but the prevailing thinking is that this creates confusion and sloppy programming.
Last you have the data store. It is usually a backend multitasking kind of database.
The web server servers up a stream of HTML to a client browser. The browser knows HTML and sometime a little Java so it displays a form. The form when completed is passed to the web server again creating a new thread. The web server passes the input of the form to your script. The script receives the input and processes it. If the input is to be stored in a database, the script must establish an interface to the backend and pass the data to it. I wish I could simplify it for you, but the complexity involved requires considerable effort. If I were you, I would print out the HOWTO provided by the operating system and begin reading. Then experiment with everything until its all working.
I would try to get one thing working. Once I had it working then I would move to the next thing.
Leland
Leland F. Jackson, CPA
Software - Master (TM)
Nothing Runs Like the Fox