reorder section 'Getting a Signed SSL Certificate';
authorSteve Sheppard <ssheps@gmail.com>
Thu, 16 Sep 2010 16:22:55 +0000 (12:22 -0400)
committerSteve Sheppard <ssheps@gmail.com>
Thu, 16 Sep 2010 16:22:55 +0000 (12:22 -0400)
1.6/admin/ServersideInstallation.xml

index db6897c..0eab0da 100644 (file)
                                </para>
                        </section>
                </section>
+               <section xml:id="serversideinstallation-ssl">
+                       <title>Getting a Signed SSL Certificate</title>
+                       <para>This section describes how to get a properly signed SSL certificate.</para>
+                       <para>For temporary testing purposes, you can use the command <command>openssl</command> to create a new SSL key for your Apache server. This is just a self-signed certificate and will generate warnings in the Staff Client and browser during testing and development. For a public production server you should configure or purchase a properly signed SSL certificate.</para>
+                       <indexterm>
+                               <primary>ZZZ-REVIEW</primary>
+                               <secondary>ADD INFO ON HOW TO GET A SIGNED SSL CERTIFICATE </secondary>
+                       </indexterm>
+                       <caution>ADD INFO ON HOW TO GET A SIGNED SSL CERTIFICATE </caution>
+               </section>
                <section xml:id="serversideinstallation-postgresql">
                        <title>Installing PostgreSQL</title>
                        <indexterm>
                        </section>
                </section>
        </section>
-       <section xml:id="serversideinstallation-ssl">
-               <title>Getting a Signed SSL Certificate</title>
-               <para>This section describes how to get a properly signed SSL certificate.</para>
-               <para>For temporary testing purposes, you can use the command <command>openssl</command> to create a new SSL key for your Apache server. This is just a self-signed certificate and will generate warnings in the Staff Client and browser during testing and development. For a public production server you should configure or purchase a properly signed SSL certificate.</para>
-               <indexterm>
-                       <primary>ZZZ-REVIEW</primary>
-                       <secondary>ADD INFO ON HOW TO GET A SIGNED SSL CERTIFICATE </secondary>
-               </indexterm>
-               <caution>ADD INFO ON HOW TO GET A SIGNED SSL CERTIFICATE </caution>
-       </section>
        <index/>
 </chapter>