Difference between revisions of "OPS235 Assignment 2 OLD"

From CDOT Wiki
Jump to: navigation, search
 
(103 intermediate revisions by 11 users not shown)
Line 1: Line 1:
−
[[Category:OPS235]]
+
{{Admon/caution|THIS IS AN OLD VERSION OF THE ASSIGNMENT|'''This is an archived version. Do not use this in your OPS235 course.'''}}
 +
= OPS235 Assignment 2 =
  
−
{{Admon/note|Assignment Material May Appear on Tests and Exam|Doing your assignment is part of your ongoing learning process. As such you will be tested on this material in future tests and exams. If you have any questions or need help, please consult your instructor in a timely manner. The due date for this assignment will not be extended. As it must be marked in class.
+
'''Weight:''' 5% of the overall grade
−
This assignment will be marked partially through demonstration and partially through the submission of files.}}
 
  
−
= OPS235 Assignment #2 -- Winter 2011=
+
'''Due Date:''' Week 13 <br />Refer to your instructor for submission instructions
  
−
Weight: 5% of the overall grade
 
  
−
Due Date: Week 13 - week of April 11 ('''Check with your Professor for exact date''').
+
{{Admon/important|It is YOUR responsibility to Backup your centos3 VM for this Assignment!|You are required to frequently backup your VM prior to exiting a work session during this assignment. Your instructor will NOT accept the fact that your hard disk crashed and lost all of your work. If you properly backed up your VM images and xml configuration files to a USB, then you can purchase a new hard-disk or wipe and recreate your hard disk and restore your VMs.}}<br>
−
 
 
−
{{Admon/important|Backup Your Configuration Files|Before making any changes to your system configuration, backup the original configuration files into the <code>/backups</code> directory, and use <code>git</code> to manage your change.}}
 
  
 
== Introduction and Purpose ==
 
== Introduction and Purpose ==
  
−
In this assignment, you will demonstrate the skills you have learned to this point by configuring two services: a database server and a web server. You will install and use a database-backed web application, MediaWiki, to show that these services have been installed properly. Finally, you will configure the SELinux security system and the web server to serve files in the <code>public_html</code> subdirectory of each user's home directory, including a short web script.
+
In this assignment, you will demonstrate the skills you have learned to this point by configuring two services: a '''database server''' and a '''web server'''. You will install and use a database-backed web application, '''Wordpress''', to show that these services have been installed properly. You will also configure the '''SELinux''' security system to further enhance the security of your computer system.
−
 
 
−
In this assignment, you will attempt to maintain a high level of security, by using SELinux and the iptables firewall to guard against unauthorized access.
 
−
 
 
−
This lab may be performed using any combination of your virtual machines and/or host disk pack.
 
−
 
 
−
== About SELinux ==
 
−
 
 
−
SELinux stands for ''Security Enhanced Linux'' and is based on research performed at NSA and other locations. Where the normal Unix/Linux security system, based upon file permissions, is a ''discretionary access control'' system (DAC), SELinux is a ''mandatory access control'' system (MAC). This means that it attempts to enforce a consistent policy across the entire system, on top of the settings that any user has configured.
 
−
 
 
−
SELinux decisions are based on the ''security context'' of system resources such as files and processes. The security context consists of a user, role, type, and sensitivity component; you can see the security context of files and processes by adding the <code>-Z</code> option to the <code>ls</code> and <code>ps</code> commands:
 
−
 
 
−
$ ls -lZ
 
−
drwxr-xr-x. root  root  '''system_u:object_r:file_t:s0'''          arm
 
−
drwxr-xr-x. chris chris '''unconfined_u:object_r:user_home_t:s0''' arm2
 
−
drwxrwxr-x. chris chris '''unconfined_u:object_r:user_home_t:s0''' bin
 
−
drwxr-xr-x. chris chris '''unconfined_u:object_r:user_home_t:s0''' Desktop
 
−
drwxr-xr-x. chris chris '''unconfined_u:object_r:user_home_t:s0''' Documents
 
−
drwxr-xr-x. chris chris '''unconfined_u:object_r:user_home_t:s0''' Downloads
 
−
-rw-------. chris chris '''unconfined_u:object_r:user_home_t:s0''' fedora0.ks
 
−
-rw-------. chris chris '''unconfined_u:object_r:user_home_t:s0''' fedora1.ks
 
−
-rw-------. chris chris '''unconfined_u:object_r:user_home_t:s0''' fedora2.ks
 
−
-rw-------. chris chris '''unconfined_u:object_r:user_home_t:s0''' fedora3.ks
 
−
-rw-rw-r--. chris chris '''unconfined_u:object_r:user_home_t:s0''' foo
 
−
-rw-r--r--. chris chris '''unconfined_u:object_r:user_home_t:s0''' hosts
 
−
drwxr-xr-x. chris chris '''unconfined_u:object_r:user_home_t:s0''' Music
 
−
drwxr-xr-x. chris chris '''unconfined_u:object_r:user_home_t:s0''' Pictures
 
−
drwxrwxr-x. chris chris '''unconfined_u:object_r:user_home_t:s0''' play
 
−
drwxr-xr-x. chris chris '''unconfined_u:object_r:user_home_t:s0''' Public
 
−
drwxr-xr-x. chris chris '''unconfined_u:object_r:user_home_t:s0''' Templates
 
−
drwxr-xr-x. chris chris '''unconfined_u:object_r:user_home_t:s0''' Videos
 
−
-rw-r--r--. chris chris '''unconfined_u:object_r:user_home_t:s0''' x
 
−
[chris@muskoka ~]$ ps -Z
 
−
LABEL                                                  PID TTY      TIME CMD
 
−
'''unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023''' 2595 pts/1 00:00:00 bash
 
−
'''unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023''' 2612 pts/1 00:00:00 ps
 
−
 
 
−
The SELinux policy controls the interactions between security contexts. For example, the policy may specify that the Apache httpd webserver cannot read files in <code>/etc</code>, so if an attacker finds a way to make httpd (or a script run by httpd) read a file in <code>/etc</code>, SELinux will recognize that this is not normal and will deny the access. Since this is done at the kernel level, httpd will get a "file not found" error, even though the file is present, and there is no way for httpd to work around that error.
 
−
 
 
−
=== SELinux Context Commands ===
 
−
 
 
−
There are two main commands used to set the SELinux security context of files:
 
−
# chcon - sets the security context of a file to a particular value
 
−
#* Example: setting the ''type'' of a file: <code>chcon -t ''unconfined_t'' ''/tmp/foo''</code>
 
−
#* Example: setting the user/role/type of a file: <code>chcon ''unconfined_u:object_r:user_home_t'' ''~/foo''</code>
 
−
# restorecon - resets the default security context of a file
 
−
#* Example: reset the context of one file: <code>restorecon /etc/services</code>
 
−
#* Example: recursively reset the contexts of all of the files in a directory: <code>restorecon -R ~</code>
 
−
 
 
−
You can reset the default security context of the entire system at the next boot with this command:
 
  
−
touch /.autorelabel
+
'''NOTE: Do this assignment inside the centos3 virtual machine. '''
  
−
=== SELinux Booleans ===
+
== Installing Packages==
  
−
SELinux policy can be tuned (without writing an entirely new policy) through the use of ''booleans'' or option switches. Each boolean can have a value of on (1) or off (0).
+
<u>Install these packages using ''yum''</u>
  
−
The <code>getsebool</code> and <code>setsebool</code> commands can be used to view and set SELinux boolean values:
+
* '''httpd''' - this is the Apache web server software.
−
 
+
* '''php''' - this is the PHP server software, which allows Apache to run more complex websites.
−
{|class="mediawiki sortable" border="1" cellspacing="0"
+
* '''php-mysql''' - this is a PHP extension that allows PHP to use a MySQL server.
−
!Command
 
−
!Description
 
−
|-
 
−
|<code>getsebool -a</code>
 
−
|Displays all SELinux booleans
 
−
|-
 
−
|<code>getsebool ''foo''</code>
 
−
|Displays the SELinux boolean ''foo''
 
−
|-
 
−
|<code>setsebool ''foo'' ''value''</code>
 
−
|Sets the SELinux boolean ''foo'' to ''value'' (where ''value'' is 0 or "off", or 1 or "on")
 
−
|}
 
  
  
−
=== SELinux Graphical Tools ===
+
<u>Install the '''mysql-server''' (MySQL database server) package</u>
  
−
The ''system-config-selinux'' tool, which is on the menu as System>Adminstration>SELinux Management, provides a GUI for managing SELinux booleans and more.
+
'''NOTE:''' This package may not be in the main repository. There a couple of options:
  
 +
:*'''Preferred method:''' Use an alternative package (for example: '''mariadb''' and '''mariadb-server''')
 +
:*Download a "zipped tar-ball" from a website (google-search), decompress, and compile
  
−
{{Admon/note|Takes Notes!|Take detailed notes of the steps you perform from this point onward -- you will need them for the wiki pages you will create later.}}
+
== Configuring Apache ==
  
−
== Installing Packages ==
+
# Start the httpd service using '''systemctl'''.
 +
# Ensure that the httpd service starts automatically during boot.
 +
# Confirm that you can connect to your web server using a web browser -- both from centos3 (you can test using '''links''') as well as from the host. You should see the Apache Test Page.
 +
# If you can't connect to it from outside the machine - perhaps your firewall is blocking access to the web server.
  
−
Install these packages using ''yum'':
+
== Configuring MySQL ==
−
* '''httpd''' - this is the Apache web server software. It provides the '''httpd''' service, which runs on port 80.
 
−
* '''php''' - this is the PHP server software. It provides the '''php''' capabilities to the web server and wiki.
 
−
* '''mysql-server''' - this is the MySQL database server. It provides the '''mysqld''' service, which runs on a Unix domain socket and TCP port 3306 by default.
 
−
* '''mediawiki''' - this is the wiki software used by this wiki, Wikipedia, and many other sites. It is a series of PHP scripts which are run by Apache httpd as requests are received, and it connects to a database such as MySQL locally or on other servers.
 
  
−
== Configuring Services ==
+
# Start the MySQL service (mysqld or mariadb) using '''systemctl'''.
 +
# Ensure that the mysqld/mariadb service starts automatically during boot.
 +
# You may get messages after starting the MySQL service for the first time. Do not ignore these messages, it  will tell you how to set a password and take other basic steps to secure the the MySQL server. Follow those instructions to set a password, recording the detail of what you do for later use.
 +
#* If you do not see any messages, research how you can secure the MySQL installation and set the MySQL-root password.
 +
#* Read those messages carefully, you are setting up a production MySQL server and there shouldn't be any "test" databases or anonymous users or users without a password.
 +
# Set your MySQL root password to your learn ID (without the @senecac.on.ca part).
 +
# This following part is challenging so take your time and read the instructions to make sure you do it properly, we have to set up a dedicated user and database for wordpress:
 +
## Start by looking at http://codex.wordpress.org/Installing_WordPress#Using_the_MySQL_Client where you will find instructions for the setup.
 +
## You will need to run those commands in a centos3 terminal.
 +
## Your adminusername is root
 +
## Your databasename is myblog
 +
## Your wordpressusername is your learn ID
 +
## The password should also be your learn ID
 +
## Your hostname is localhost
  
−
=== Apache httpd ===
+
== Installing and Configuring Wordpress ==
  
−
# Start the httpd service using the '''service''' command.
+
Wordpress (like most web applications) is not available in the Fedora repositories, it must be downloaded and installed manually.
−
# Confirm that you can connect to your web server using a web browser -- both from the machine on which the server is running as well as from another machine on the same network. You should see a test page.
 
−
# Configure this software to start when the system is booted.
 
−
# Create a very simple HTML index page for your system, and place it at <code> /var/www/html/index.html </code>
 
−
# Confirm that you can view the index page. If not, adjust your iptables configuration as necessary, or check for errors in <code>/var/log/httpd</code>
 
  
−
=== MySQL ===
+
# Download the latest .tar.gz version from wodpress.org into your centos3 (use wget).
−
 
+
# Extract it into '''/var/www/html'''
−
# Start the MySQL service (mysqld).
+
# Now we need to allow Apache to modify the wordpress installation. To do this use chown -R to make the owner and group of every file and directory inside wordpress "apache".
−
# '''When started for the first time, this service will print a message telling you how to set a password and take other basic steps to secure the the MySQL server.''' Follow those instructions to set a password, recording the detail of what you do for later use.
+
# Check your work so far by pointing your web browser to http://centos3/wordpress/ where you will get an error starting with "There doesn't seem to be a wp-config.php file"
−
# Configure this software to start when the system is booted.
+
# Copy the wp-config-sample.php file to wp-config.php and edit the new file:
−
 
+
#* Change the DB_NAME, DB_USER, DB_PASSWORD to the appropriate values.
−
=== MediaWiki ===
+
# Now go back to http://centos3/wordpress/ - you should see a Wordpress Welcome/Setup page.
−
 
+
#* Set the title to Your Name's Blog. For example for me it would be "Andrew Smith's Blog"
−
# Edit MediaWiki's httpd configuration file, <code>/etc/httpd/conf.d/mediawiki.conf</code>
+
#* Set the password to your learn ID.
−
#* Uncomment the first two <code>Alias</code> lines
+
#* Set the email to your Seneca email address.
−
#* Reload the httpd configuration using the <code>service</code> command
+
#* Click "Install Wordpress", you should see a "Success!" message.
−
# Access <code>http://localhost/wiki</code> on the machine on which the web server is running (this will not work if done remotely, unless you use an ssh tunnel so that the access appears to be coming from the local host). You will see the MediaWiki welcome page; click on the setup link.
 
−
# Enter the setup information for your wiki:
 
−
#* Enter a name for the wiki
 
−
#* Enter your learn e-mail address as the contact information
 
−
#* Disable all e-mail features
 
−
#* Leave the database host as "localhost"
 
−
#* Set up a database password
 
−
#* Get MediaWiki to set up the superuser account by checking the appropriate box and entering the superuser password ('''Note:''' This is the database superuser password, NOT the root password).
 
−
# Click the "Install MediaWiki!" button.
 
−
# Once the setup is complete, you will need to move a file within the MediaWiki directory (i.e. inside <code>/var/www/wiki</code>). Refer to the directions in the confirmation web page.
 
−
 
 
−
When you are done, you should be able to go to <code>http://'''hostname'''/wiki</code> from any directly-connected machine.
 
−
 
 
−
=== Serving Personal Web Pages ===
 
−
 
 
−
# Configure httpd to serve the <code>~/public_html</code> directories of your users. This will require changes to <code>/etc/httpd/conf/httpd.conf</code> as well as the SELinux configuration. See the man page for <code>httpd_selinux</code> and the Apache [http://httpd.apache.org/docs/2.2/ httpd documentation] for details.
 
−
# Prove that this works by creating a page in your <code>~/public_html</code> directory. The URL will be <code>http://''hostname''/~''your-user-id''/</code>
 
−
# Create a short web script which displays the available disk space on the computer. At its most basic level, a web script is the same as a regular script, with this additional requirement:
 
−
#* It must output the line "Content-type: text/plain" or "Content-type: text/html" (depending on whether the script output is plain text or HTML), followed by a blank line.
 
−
# Name the script <code>~/public_html/diskfree.cgi</code> - The URL will be <code>http://''hostname''/~''your-user-id''/diskfree.cgi</code>
 
−
# Configure httpd and SELinux to allow your script to be run from the web. This will require changes to <code>/etc/httpd/conf/httpd.conf</code> as well as the SELinux configuration (possibly including both booleans and SELinux context). As with step 1, see the man page for <code>httpd_selinux</code> and the Apache [http://httpd.apache.org/docs/2.2/ httpd documentation] for details.
 
−
 
 
−
{{Admon/tip|Hint|Look for an "add-handler" line in your httpd.conf file.}}
 
  
 
== Write-up ==
 
== Write-up ==
  
−
Create a high-quality write-up of this assignment on your wiki. '''Describe in detail exactly what you did to set up each component'''. Include at least these pages:
+
Write a blog post on your new blog explaining:
−
# A main page (page name Main Page), describing in general terms what you did and containing links to the other wiki pages, as well as a link to the page and the script in your <code>~/public_html</code> directory.
+
* What is Apache, PHP, MySQL, and Wordpress.
−
# A page for your httpd configuration (page name httpd_conf). Along with a description, include the exact text of your httpd.conf file.
+
* What problems (minor and major) you ran into during the installation and how you solved them.
−
# A page for your MySQL configuration (page name mysql_conf). Along with a description, include the details of the steps you performed to set up MySQL.
 
−
# A page for your SELinux configuration (page name selinux_conf). Along with a description, include a list of all of your booleans and their current settings. Show that the configuration is as tight as possible (e.g., don't change booleans unnecessarily).
 
−
# A page for your MediaWiki configuration (page name mediawiki_conf). Along with a description, include your MediaWiki configuration file.
 
−
# A page for your iptables configuration (page name iptables_conf). Show the exact iptables rules that are in effect. Demonstrate that the configuration is as tight as possible (for example, test access to other services, and include the results of those tests in the wiki page).
 
−
 
−
The easiest way to create new page is to create a link to it from an existing page (such as the main page), and then follow that link.
 
  
−
'''Write well and be creative:'''
+
Write a second post on your blog explaining:
−
* Make sure your spelling and grammar are correct (they count!).
+
* Are you ready for the exam or not.
−
* Present the pages attractively, and take advantage of graphics, colour, and fonts as appropriate -- for example, you may want to highlight the changes that you made in the configuration files using '''bold''' print, use outline numbering, divide the pages into easy-to-navigate sections, or use colour to show the <span style="color:orange">commands you typed</span> and <span style="color:green">what the system displayed in response</span>.
+
* List the material you are strong on.
−
* Stick to the important information - avoid including excessive text which doesn't add to the content that you are presenting (remember, your professor will be reading hundreds of wiki pages while marking!).
+
* List the material you are worried about.
 +
* List any questions or topics you would like me to address during exam review.
  
−
Resources on wiki markup:
+
''' Make your posts look professional. That means use good english, headings, bullet or numbered lists, etc.
−
* [http://en.wikipedia.org/wiki/Help:Wiki_markup Wiki markup] - Wikipedia
 
−
* [[Sandbox|Sandbox page on this wiki]] - examples
 
  
−
{{Admon/tip|Bonus Opportunity!|Change the default icon in the upper-left corner of your MediaWiki installation to a picture of your choosing. Be sure that you have copyright clearance to use that image (e.g., it is licensed to you, or it is a picture you own).}}
+
== Submitting Your Assignment ==
  
−
== Submitting the Assignment ==
+
'''Due date:''' Your name will be called in the lab on the due date for the assignment. If you are not there when your name is called - you will lose 20% of your mark. In that case you may show me your submission in the second lab that week instead. Assignments submitted after that will receive a grade of 0, but must still be completed satisfactorily in order to pass the course.
  
−
Your professor will require you to submit this assignment in at least one of two ways:
+
=== Ready to show ===
  
−
# Demonstrate that the wiki is working.
+
Open one or more terminals in c7host, SSH to centos3 from those terminals, and have the following ready:
−
# Use wget to harvest the wiki pages:
+
* The correct RPMs are installed
−
#* Make sure all of the <code><nowiki>http://</nowiki></code>-style links (for the wiki image, the link to diskfree.cfgi, and so forth) use the same hostname (don't use "localhost" for one and "f13host" for another, for example).
+
* Output showing firewall has been properly set up
−
#* Issue the command: <code>wget -prk http://''hostname''/wiki</code> -- where ''hostname'' matches the hostname used in the <code><nowiki>http://</nowiki></code> links in your wiki pages.
+
* Output of chkconfig --list mysqld
−
#* Create a compressed tar file containing the results. (name the file <learnid>-a2.tgz)
+
* Output of chkconfig --list httpd
−
#* Check the tar file to see that it contains everything necessary to view your site (in particular, check that all needed image files are included). Do not edit the files in the tar archive -- if changes are needed, modify your wiki, and then repeat the <code>wget</code> and <code>tar</code> steps above.
+
* MySQL output of: show databases; use mysql; select User,Password from user; use myblog; show tables;
−
#* Submit the tar file to your professor in the manner he specifies.
+
* Output of ls -la /var/www/html/wodpress/
 +
* Output of head -30 /var/www/html/wodpress/wp-config.php
 +
* Open a firefox with http://centos3/wordpress/
  
−
=== Section A - Raymond Chan ===
+
=== Rubric ===
  
−
* Submit online through this link https://cs.senecac.on.ca/~rchan/ops235/asgm2/ by 3:15 pm, Monday, April 11, 2011.
+
{| class="wikitable" border="1"
 +
! Task !!  Maximum mark !! Actual mark
 +
|-
 +
| Correct packages installed || 1 ||
 +
|-
 +
| Firewall setup properly || 2 ||
 +
|-
 +
| Apache set up and running || 2 ||
 +
|-
 +
| MySQL set up correctly || 3 ||
 +
|-
 +
| Wordpress extracted correctly || 1 ||
 +
|-
 +
| Wordpress set up correctly || 2 ||
 +
|-
 +
| Wordpress showing in Firefox || 1 ||
 +
|-
 +
| Everything ready to show || 2 ||
 +
|-
 +
| First blog post || 3 ||
 +
|-
 +
| Second blog post || 3 ||
 +
|-
 +
| '''Total''' || 20 ||
  
−
=== Sections B & C - Brian Gray ===
+
|}
  
−
* See your professor for submission instructions and due date.
+
[[Category:OPS235]]
−
 
 
−
=== Sections D, E & F - Murray Saul ===
 
−
 
 
−
* Check most recent learn e-mail (Tuesday April 12th @ 11:00 a.m.) for modified submission instructions.
 
−
 
 
−
=== Section G - Chris Tyler ===
 
−
 
 
−
* Submit online through this link: https://cs.senecac.on.ca/~ctyler/ops235/a2/ by 11:59 pm, Thursday, April 14.
 
−
 
 
−
== Assessment ==
 
−
 
 
−
* 50% - completion of steps - quality of configuration, iptables and SELinux configuration as tight as possible
 
−
* 50% - documentation on the wiki - quality of writing, quality of presentation, and accuracy and completeness of information
 
−
* +5% - bonus for replacing the wiki logo
 

Latest revision as of 12:02, 27 November 2019

Stop (medium size).png
THIS IS AN OLD VERSION OF THE ASSIGNMENT
This is an archived version. Do not use this in your OPS235 course.

OPS235 Assignment 2

Weight: 5% of the overall grade

Due Date: Week 13
Refer to your instructor for submission instructions


Important.png
It is YOUR responsibility to Backup your centos3 VM for this Assignment!
You are required to frequently backup your VM prior to exiting a work session during this assignment. Your instructor will NOT accept the fact that your hard disk crashed and lost all of your work. If you properly backed up your VM images and xml configuration files to a USB, then you can purchase a new hard-disk or wipe and recreate your hard disk and restore your VMs.

Introduction and Purpose

In this assignment, you will demonstrate the skills you have learned to this point by configuring two services: a database server and a web server. You will install and use a database-backed web application, Wordpress, to show that these services have been installed properly. You will also configure the SELinux security system to further enhance the security of your computer system.

NOTE: Do this assignment inside the centos3 virtual machine.

Installing Packages

Install these packages using yum

  • httpd - this is the Apache web server software.
  • php - this is the PHP server software, which allows Apache to run more complex websites.
  • php-mysql - this is a PHP extension that allows PHP to use a MySQL server.


Install the mysql-server (MySQL database server) package

NOTE: This package may not be in the main repository. There a couple of options:

  • Preferred method: Use an alternative package (for example: mariadb and mariadb-server)
  • Download a "zipped tar-ball" from a website (google-search), decompress, and compile

Configuring Apache

  1. Start the httpd service using systemctl.
  2. Ensure that the httpd service starts automatically during boot.
  3. Confirm that you can connect to your web server using a web browser -- both from centos3 (you can test using links) as well as from the host. You should see the Apache Test Page.
  4. If you can't connect to it from outside the machine - perhaps your firewall is blocking access to the web server.

Configuring MySQL

  1. Start the MySQL service (mysqld or mariadb) using systemctl.
  2. Ensure that the mysqld/mariadb service starts automatically during boot.
  3. You may get messages after starting the MySQL service for the first time. Do not ignore these messages, it will tell you how to set a password and take other basic steps to secure the the MySQL server. Follow those instructions to set a password, recording the detail of what you do for later use.
    • If you do not see any messages, research how you can secure the MySQL installation and set the MySQL-root password.
    • Read those messages carefully, you are setting up a production MySQL server and there shouldn't be any "test" databases or anonymous users or users without a password.
  4. Set your MySQL root password to your learn ID (without the @senecac.on.ca part).
  5. This following part is challenging so take your time and read the instructions to make sure you do it properly, we have to set up a dedicated user and database for wordpress:
    1. Start by looking at http://codex.wordpress.org/Installing_WordPress#Using_the_MySQL_Client where you will find instructions for the setup.
    2. You will need to run those commands in a centos3 terminal.
    3. Your adminusername is root
    4. Your databasename is myblog
    5. Your wordpressusername is your learn ID
    6. The password should also be your learn ID
    7. Your hostname is localhost

Installing and Configuring Wordpress

Wordpress (like most web applications) is not available in the Fedora repositories, it must be downloaded and installed manually.

  1. Download the latest .tar.gz version from wodpress.org into your centos3 (use wget).
  2. Extract it into /var/www/html
  3. Now we need to allow Apache to modify the wordpress installation. To do this use chown -R to make the owner and group of every file and directory inside wordpress "apache".
  4. Check your work so far by pointing your web browser to http://centos3/wordpress/ where you will get an error starting with "There doesn't seem to be a wp-config.php file"
  5. Copy the wp-config-sample.php file to wp-config.php and edit the new file:
    • Change the DB_NAME, DB_USER, DB_PASSWORD to the appropriate values.
  6. Now go back to http://centos3/wordpress/ - you should see a Wordpress Welcome/Setup page.
    • Set the title to Your Name's Blog. For example for me it would be "Andrew Smith's Blog"
    • Set the password to your learn ID.
    • Set the email to your Seneca email address.
    • Click "Install Wordpress", you should see a "Success!" message.

Write-up

Write a blog post on your new blog explaining:

  • What is Apache, PHP, MySQL, and Wordpress.
  • What problems (minor and major) you ran into during the installation and how you solved them.

Write a second post on your blog explaining:

  • Are you ready for the exam or not.
  • List the material you are strong on.
  • List the material you are worried about.
  • List any questions or topics you would like me to address during exam review.

Make your posts look professional. That means use good english, headings, bullet or numbered lists, etc.

Submitting Your Assignment

Due date: Your name will be called in the lab on the due date for the assignment. If you are not there when your name is called - you will lose 20% of your mark. In that case you may show me your submission in the second lab that week instead. Assignments submitted after that will receive a grade of 0, but must still be completed satisfactorily in order to pass the course.

Ready to show

Open one or more terminals in c7host, SSH to centos3 from those terminals, and have the following ready:

  • The correct RPMs are installed
  • Output showing firewall has been properly set up
  • Output of chkconfig --list mysqld
  • Output of chkconfig --list httpd
  • MySQL output of: show databases; use mysql; select User,Password from user; use myblog; show tables;
  • Output of ls -la /var/www/html/wodpress/
  • Output of head -30 /var/www/html/wodpress/wp-config.php
  • Open a firefox with http://centos3/wordpress/

Rubric

Task Maximum mark Actual mark
Correct packages installed 1
Firewall setup properly 2
Apache set up and running 2
MySQL set up correctly 3
Wordpress extracted correctly 1
Wordpress set up correctly 2
Wordpress showing in Firefox 1
Everything ready to show 2
First blog post 3
Second blog post 3
Total 20
Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=OPS235_Assignment_2_OLD&oldid=142281"