 |
Home
> Project 1 • Introduction • Narrative
• Instructions • Functionality
• Extras •
|
Introduction
For my first INLS 183 project, I chose to get the Apache server running
on my group's box. As a group, we decided on each containing our own
Apache servers within our personal directories so that we could each
customize our servers without fear of having our files overwritten
or wiped out through no fault of our own.
I chose to install Apache so that I can eventually add more components
to it and try and tweak it. I see Apache as the foundation upon which
most of my future projects will build upon. Its also required for
this class that I set up a server or daemon. |
|
Narrative
Installation of Apache in my file system on my group's Linux box was
relatively straightforward. I started by logging into my computer
via ssh telnet from a remote laptop. I then set up a few folders for
future use; one named "scripts" for saving my session logs
throughout the class, and one named "server" for eventually
holding my Apache files.
After setting up these directories I tried to ftp the Apache g-zipped
file from the Apache website. I switched to ftp in my telnet session,
then tried to connect to the Apache site. This was not successful.
the reason for my inability to connect to the Apache site was that
I was trying to connect to "http://www.apache.org", where
i could see the file I wanted in my Web browser.
At this point, after about 15 minutes of frustration, I remembered
the "wget" command from class. I quit ftp and simply typed
"wget" and the address of the file I wanted. Viola, the
file downloaded into my "server" folder. I now had the Apache
gzipped file, which I un-gzipped and then untarred. After
opening the "INSTALL" file via pico, I saw the directions
for setting up Apache (config, make, make install) and set to work.
Next
I began the configuration process, and set up my config prefix to
actually install for "/apache/apache2.0.40". At this point
I opened a second telnet terminal and created the appropriate folder
structure off my home directory. I ran the configuration, then the
make files. Everything went off without a hitch and I soon had a jumble
of files in my apache2.0.40 folder.
After consulting the Apache website, I opened the conf folder in my
apache2.0.40 folder and the httpd.conf file with pico. At some point
I made a backup of this file as well. In the httpd.conf file, I set
up my port (to 8081) and my server admin information. Then I saved
and closed the file.
In a separate terminal, I entered the bin folder and attempted to
start the Apache server with "apachectl". Of course, it
was about time for something to go wrong, and Linux kept giving me
a message that it could not find "apachectl". I was looking
right at it, but could not figure out how to get it to run. At this
point, I emailed Professor Newby about the issue I was having and
went to bed.
The next day after class, I checked my email and I had a general response
to my general email sent out the night before. The content of the
email was enough for me to realize my error though (which was that
I forgot to start the command with the "./" sequence), so
I started up another script and then went off to try and start my
Apache server.
With this key, the server started right up, and was purring like a
kitten. I then went into the "htdocs" folder, and edited
the "index.html.en" page, adding a note to a friend of mine.
I asked her to check it on another computer, and i checked it on mine,
and we both were able to see the correct page!
At this point, I accomplished what i set out to do, satisfied all
the requirements of the project, and started putting this report together.
(Oh yeah, I shut down my server too.) |
|
Instructions
for use
I am not sure what to say here, but if my server is running, you can
access it through the URL "red.ils.unc.edu:8081".
|
|
Functionality
It does work! |
|
Files
and Baubles screen shots, script files, extras
• My first day's script file
• My second day's script file
• Link to red.ils.unc.edu:8081
• A screen capture of
my server running and serving the index.html.en page. |
|
|