Merge lp:~evarlast/serverguide/wordpress into lp:~ubuntu-core-doc/serverguide/quantal

[Jay R. Wren]

I was surprised that WordPress was not listed in the lamp applications section, so I wrote a wordpress sub section

[Peter Matulis (petermatulis)]

XML does not validate. Please correct this today as String Freeze is upon us.

====
scripts/validate.sh serverguide/C/serverguide.xml
 --Validating serverguide/C/serverguide.xml ...
lamp-applications.xml:607: element para: validity error : Element a is not declared in para list of possible children
lamp-applications.xml:608: element a: validity error : No declaration for element a
lamp-applications.xml:608: element a: validity error : No declaration for attribute href of element a
Document serverguide/C/serverguide.xml does not validate
====

review: Needs Fixing

[Doug Smythies (dsmythies)]

Thanks for your good work on this new section. Would you consider having a look at, and trying to fix, the validation issues? While this merge proposal is for quantal, it would be great to get it into the 13.04 server guide.

[Jay R. Wren (evarlast)]

looking into it.

[lp:~evarlast/serverguide/wordpress]

87. By Jay R. Wren on 2013-02-23

oops, fixed a ahref that should have been ulink url

88. By Jay R. Wren on 2013-02-24

merging upstream

89. By Jay R. Wren on 2013-02-24

WordPress section: use a2ensite instead of ln -s & clarify config-VHOST.php file

90. By Jay R. Wren on 2013-03-02

merge with upstream

91. By Jay R. Wren on 2013-03-02

WordPress section: remove link to a blog

linking to blog documentation is not recommended. I've removed the link.

92. By Jay R. Wren on 2013-03-03

change wordpress references to MLA format

http://www.easybib.com/reference/guide/mla/website

Unmerged revisions

=== modified file 'serverguide/C/databases.xml'
--- serverguide/C/databases.xml	2012-04-06 20:16:46 +0000
+++ serverguide/C/databases.xml	2012-07-27 20:53:22 +0000
@@ -324,25 +324,25 @@
             <para>By default, connection via TCP/IP is disabled.
             PostgreSQL supports multiple client authentication methods.
             IDENT authentication method is used for <application>postgres</application> and local users, unless otherwise configured.  
-	    Please refer <ulink url="http://www.postgresql.org/docs/8.4/static/admin.html">
+	    Please refer <ulink url="http://www.postgresql.org/docs/9.1/static/admin.html">
 	    the PostgreSQL Administrator's Guide if you would like to configure alternatives like Kerberos</ulink>.
 	    </para>
             <para>The following discussion assumes that you wish to enable 
             TCP/IP connections and use the MD5 method for client 
             authentication. PostgreSQL configuration files are stored in the
             <filename>/etc/postgresql/&lt;version&gt;/main</filename>
-            directory. For example, if you install PostgreSQL 8.4, the
+            directory. For example, if you install PostgreSQL 9.1, the
             configuration files are stored in the
-            <filename>/etc/postgresql/8.4/main</filename> directory.
+            <filename>/etc/postgresql/9.1/main</filename> directory.
             </para>
             <tip>
             <para>
              To configure <emphasis>ident</emphasis>
-             authentication, add entries to the <filename>/etc/postgresql/8.4/main/pg_ident.conf</filename>
+             authentication, add entries to the <filename>/etc/postgresql/9.1/main/pg_ident.conf</filename>
              file.  There are detailed comments in the file to guide you.
             </para>
             </tip>
-            <para>To enable TCP/IP connections, edit the file <filename>/etc/postgresql/8.4/main/postgresql.conf</filename></para>
+            <para>To enable TCP/IP connections, edit the file <filename>/etc/postgresql/9.1/main/postgresql.conf</filename></para>
             <para>
 	    Locate the line <emphasis>#listen_addresses = 'localhost'</emphasis> and change it to:
 	    </para>
@@ -381,7 +381,7 @@
 </screen>
             <para>
 	    After configuring the password, edit the file
-            <filename>/etc/postgresql/8.4/main/pg_hba.conf</filename> to use
+            <filename>/etc/postgresql/9.1/main/pg_hba.conf</filename> to use
             <emphasis>MD5</emphasis> authentication with the <emphasis>postgres</emphasis> user:
             </para>
 
@@ -395,12 +395,12 @@
 	    restart <application>PostgreSQL</application>:
             </para>
 <screen>
-<command>sudo /etc/init.d/postgresql-8.4 restart</command>
+<command>sudo service postgresql restart</command>
 </screen>
             <warning>
             <para>
              The above configuration is not complete by any means. Please
-             refer <ulink url="http://www.postgresql.org/docs/8.4/static/admin.html">
+             refer <ulink url="http://www.postgresql.org/docs/9.1/static/admin.html">
 			 the PostgreSQL Administrator's Guide</ulink> to configure more parameters.
             </para>
             </warning>
@@ -410,15 +410,15 @@
           <itemizedlist>
 	    <listitem>
               <para>
-  	      As mentioned above the <ulink url="http://www.postgresql.org/docs/8.4/static/admin.html">Administrator's Guide</ulink>
-	      is an excellent resource.  The guide is also available in the <application>postgresql-doc-8.4</application> package.
+  	      As mentioned above the <ulink url="http://www.postgresql.org/docs/9.1/static/admin.html">Administrator's Guide</ulink>
+	      is an excellent resource.  The guide is also available in the <application>postgresql-doc-9.1</application> package.
 	      Execute the following in a terminal to install the package:
               </para>
 <screen>
-<command>sudo apt-get install postgresql-doc-8.4</command>
+<command>sudo apt-get install postgresql-doc-9.1</command>
 </screen>
               <para>
-	      To view the guide enter <command>file:///usr/share/doc/postgresql-doc-8.4/html/index.html</command> into the address
+	      To view the guide enter <command>file:///usr/share/doc/postgresql-doc-9.1/html/index.html</command> into the address
 	      bar of your browser. 
               </para>
 	    </listitem>

=== modified file 'serverguide/C/lamp-applications.xml'
--- serverguide/C/lamp-applications.xml	2012-04-06 20:16:46 +0000
+++ serverguide/C/lamp-applications.xml	2012-07-27 20:53:22 +0000
@@ -502,4 +502,138 @@
 
     </sect2>
   </sect1>
+  <sect1 id="wordpress" status="review">
+      <title>WordPress</title>
+      <para>
+          Wordpress is a blog tool, publishing platform and CMS 
+          implemented in PHP and licensed under the GNU GPLv2.
+      </para>
+      <sect2 id="wordpress-installation" status="review">
+          <title>Installation</title>
+          <para>To install <application>WordPress</application>, run the following
+              comand in the command prompt:
+          </para>
+
+<screen>
+    <command>sudo apt-get install wordpress</command>
+</screen>
+          
+           <para>
+           You should also install <application>apache2</application> web
+           server and mysql server. For installing <application>apache2</application> web
+           server, please refer to <xref linkend="http-installation"/>
+           sub-section in <xref linkend="httpd"/> section.
+            For installing <application>mysql</application> server, please refer
+            to <xref linkend="mysql-installation"/> sub-section in 
+            <xref linkend="mysql"/> section.
+           </para> 
+
+       </sect2>
+       <sect2 id="wordpress-configuration" status="review">
+           <title>Configuration</title>
+
+           <para>
+               For configuring your first WordPress application, configure an apache site.
+               Open <filename>/etc/apache2/sites-available/wordpress</filename> and write the
+               following lines:
+           </para>
+
+           <programlisting>
+        Alias /blog /usr/share/wordpress
+        Alias /blog/wp-content /var/lib/wordpress/wp-content
+        &lt;Directory /usr/share/wordpress&gt;
+            Options FollowSymLinks
+            AllowOverride Limit Options FileInfo
+            DirectoryIndex index.php
+            Order allow,deny
+            Allow from all
+        &lt;/Directory&gt;
+        &lt;Directory /var/lib/wordpress/wp-content&gt;
+            Options FollowSymLinks
+            Order allow,deny
+            Allow from all
+        &lt;/Directory&gt;
+           </programlisting>
+
+        <para>Enable this new WordPress site</para>
+
+<screen>
+<command>cd /etc/apache2/sites-enabled</command>
+<command>sudo ln -s ../sites-available/wordpress</command>
+</screen>
+
+         <para>
+         Once you configure the <application>apache2</application> web server and
+         make it ready for your <application>WordPress</application>
+         application, you should restart it. You
+         can run the following command to restart the
+         <application>apache2</application> web server:
+         </para>
+
+<screen>
+<command>sudo service apache2 restart</command>
+</screen>
+
+        <para>
+        Now configure <application>WordPress</application> to use a mysql database.
+        Open <filename>/etc/wordpress/config-localhost.php</filename> file and write
+        the following lines:
+        </para>
+
+<programlisting>
+&lt;?php
+define('DB_NAME', 'wordpress');
+define('DB_USER', 'wordpress');
+define('DB_PASSWORD', 'yourpasswordhere');
+define('DB_HOST', 'localhost');
+define('WP_CONTENT_DIR', '/var/lib/wordpress/wp-content');
+?&gt;
+</programlisting>
+        <para>Now create this mysql database. Open a temporary file with mysql commands
+        <filename>wordpress.sql</filename> and write the following lines:
+        </para>
+<programlisting>
+CREATE DATABASE wordpress;
+GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP,ALTER
+ON wordpress.*
+TO wordpress@localhost
+IDENTIFIED BY 'yourpasswordhere';
+FLUSH PRIVILEGES;
+</programlisting>
+        <para>Execute these commands.</para>
+<screen>
+<command>cat wordpress.sql | sudo mysql --defaults-extra-file=/etc/mysql/debian.cnf</command>
+</screen>
+        <para>Your new <application>WordPress</application> can now be configured by visiting
+<a href="http://localhost/blog/wp-admin/install.php">http://localhost/blog/wp-admin/install.php</a>.
+Fill out the Site Title, username, password, and E-mail and click Install WordPress.
+        </para>
+        <para>Note the generated password (if applicable) and click the login password. Your 
+<application>WordPress</application> is now ready for use.
+        </para>
+        </sect2>
+      <sect2 id="wordpress-references" status="review">
+        <title>References</title>
+
+        <itemizedlist>
+          <listitem>
+            <para>
+            For more information see the <ulink url="http://wordpress.com/">WordPress</ulink>.
+            </para>
+          </listitem> 
+          <listitem>
+            <para>
+                Also, see <ulink url="http://linux.justinhartman.com/Wordpress_Installation_on_Debian">
+                    WordPress Installation on Debian</ulink>.
+            </para>
+          </listitem> 
+          <listitem>
+            <para>
+            Also, see the <ulink url="https://help.ubuntu.com/community/WordPress">Ubuntu Wiki WordPress</ulink> page.
+            </para>
+          </listitem>
+        </itemizedlist>
+
+      </sect2>
+    </sect1>
 </chapter>

=== modified file 'serverguide/C/web-servers.xml'
--- serverguide/C/web-servers.xml	2012-04-06 20:16:46 +0000
+++ serverguide/C/web-servers.xml	2012-07-27 20:53:22 +0000
@@ -904,7 +904,7 @@
                   <para>
                      Using the excellent access control features of Squid, you may configure use of Internet services proxied by Squid
                      to be available only during normal business hours.  For example, we'll illustrate access by employees of a business
-                     which is operating between 9:00AM and 5:00PM, Monday through Friday, and which uses the 10.1.42.0/42 subnetwork:
+                     which is operating between 9:00AM and 5:00PM, Monday through Friday, and which uses the 10.1.42.0/24 subnetwork:
                   </para>
                   <para>
                      Add the following to the <emphasis role="bold">bottom</emphasis> of the ACL section of your <filename>/etc/squid/squid.conf</filename> file: