confused - http: | c: localhost etc. - where does all this server stuff go?

[shawn gibson]

I just set up a server to start doing the back end of stuff for the front end designs I build. As an avid Macromedia fan, an MS Access user, and someone who wants to learn the basics of the backend scripting languages, I'm in a bit of a conumdrum.

I've installed php/mySQL/Apache.
I've installed Macromedia Coldfusion as hopefully my mainstay.
I have the basics set up in Win2K Server.

Since I'm relying on tutorials and wizards to help learn, I'm getting totally confused as to where all this stuff is and should be going; they all go somewhere specific to the technology, and I'm guessing it's probably better for me to reset the defaults for each of them to the same root directories...is that possible? How? (I know, sorry...big dumb questions here).

Also, I keep being told to, for example, save a page at http://localhost/whatever directory/page.asp (cfm, php, etc.)...or even more frustrating, to find a page at a local http: location and modify it, and yet when I do a search for it, there's nothing there, since it's http: and not c:.

My aim ultimately is to be able to integrate Flash, Coldfusion and Dreamweaver with my MS Access databases, so I'm dealing with disparate technologies from the get-go. There are plenty of tuts on MM site, but none of it is basic enough for me to get going.

Could someone give me some pointers on what's going on, i.e., the differences between http: on a local machine, and c:? Good setup strategies for integrating roots/localhost/etc. directories...etc.

I know things are working to some extent, because I created a default page in the directory Win2K said to (i.e., localhost/default.html) and when I ipconfig my computer and paste the IP into the address in a browser, it works; and Coldfusion is up and running in the browser environment as is php/mySQL (according to the setup tests) but when I enter the same IP in my other computer that's hooked up to the net as well...my localhost/default.asp doesn't come up and the computer just hangs.

Lot's to learn, and lots out there to help, but not much at this Big Dummy level.

If I can get an answer to even one problem here, I'll be a happy camper.

Thanks everyone,

Shawn

[Dave22]

I'm sure a more knowlegable web person can address the specifics of the development end, but as for the basics:

When you are locating/opening a file using "http:", you are requesting it via the Hypertext Transfer Protocol. In other words, you have a client/server thing going on. The http protocol (in combination w/ something like Perl, ASP, etc) gains access to the local file system to read and/or write files (web pages).

When you point to the C: drive, that's opening/writing the file directly to the hard drive without going through an interim protocol.

With an http server (ie: Apache, IIS) you can create virtual servers or virtual directories that point to a specific hard drive location. For example:

Let's say you have a directory on your server's hard drive with a path of C:\WEBROOT\DIRECTORY1\MYFILES. You can create/map your web site to point directly to the "MYFILES" subdirectory and the URL (Web address) would show as "http://myserver/myfiles". You could also name the "myfiles" whatever you want (kind of like an alias name). For example, you could "label" that local path destination as "mywebsite" so that the URL would read "http://myserver/mywebsite" and it would point back to the files in your local path (C:\WEBROOT\DIRECTORY1\MYFILES).

[shawn gibson]

OK, that makes some sense. Let's say I want to re-install everything, and in the configuration stages, have everything at least begin with a c:\wwwroot, such that I could build from there, i.e.:

c:\wwwroot\dir1\default.asp
or
c:\wwwroot\dir2\dirNext\login.asp

...and then have that so that I always know how to go:

http://localhost/home.html
http://localhost/someFile.ext
(corresponding to the above "c:\wwwroot")

or

http://localhost/dir1/default.asp
http://localhost/dir1/someFile.ext
(corresponding to the above "c:\wwwroot\dir1\default.asp")

or

http://localhost/dir2/dirNext/login.asp
etc.

Thanks again

Shawn


Is it possible to do this? I will re-install everything from scratch if need be..

[Dave22]

Yep, you got the idea!