Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Minor adjustments and cleanup for remaining cookbook entries

git-svn-id: svn://cherokee-project.com/cherokee/trunk@6459 5dc97367-97f1-0310-9951-d761b3857238
  • Loading branch information...
commit 35b418b01de46d830ac0ee3e5e02eab408389a5a 1 parent 12dfa0f
taher authored
View
5 doc/cookbook_mono.txt
@@ -130,6 +130,7 @@ configuration.
important. If it is not, FastCGI will not work and you will receive
an _500 Internal Server Error_.
+.FastCGI handler
image::media/images/cookbook_mono_handler.png[FastCGI handler options]
And that is all. Once you upload your ASP.NET application to
@@ -139,9 +140,9 @@ application by pointing your web browser to, lets say
For this recipe, the package asp.net2-examples (provided by Debian and
Ubuntu thanks to some APT magic) was used. If you were to copy the
-examples to `/var/www` as final step of this tutorial, you should obtain
-something like the following screenshot.
+examples to `/var/www` as final step of this tutorial, you should see that Mono is working.
+.Demo in action
image::media/images/cookbook_mono_demo.png[Mono Demo]
When the package is installed, the examples will be placed in
View
1  doc/cookbook_moodle.txt
@@ -44,6 +44,7 @@ Simply set the `Document root` to `/var/www/moodle` and you are ready
to go. This is done within the `Basics` tab of the chosen `Virtual
Server`.
+.Custom document root
image::media/images/cookbook_moodle_document_root.png[Moodle settings]
[[moodle]]
View
20 doc/cookbook_nagios.txt
@@ -103,13 +103,31 @@ The first one will match the `/nagios/cgi-bin` directory, and will be
handled by the `CGI` handler. We will map the `/usr/local/nagios/sbin`
as the `Web Directory` for the rule, in the `Rule` tab.
+.First rule
image::media/images/cookbook_nagios1.png[cgi-bin]
+.First rule
+[options="header"]
+|====================================================================
+|Field | Value
+|Handler | CGI
+|Document root | /usr/local/nagios/sbin
+|====================================================================
+
The second one will do something similar, only mapping `/nagios` to
`/usr/local/nagios/share`.
+.Second rule
image::media/images/cookbook_nagios2.png[nagios]
+.Second rule
+[options="header"]
+|====================================================================
+|Field | Value
+|Handler | List & Send
+|Document root | /usr/local/nagios/share
+|====================================================================
+
Finally, you can set up the authentication mechanism on both rules by
configuring the `Security` tab. Choose the `Htpasswd file` validation
mechanism, write the correct Password File (the one you should have
@@ -118,8 +136,10 @@ string, `Nagios` for instance. Note that this step is optional, since
you can secure your application with any other validation mechanism
provided by Cherokee.
+.Security configuration
image::media/images/cookbook_nagios3.png[htpasswd]
And that was all for today.
+.Nagios in action
image::media/images/cookbook_nagios4.png[It's alive!]
View
2  doc/cookbook_phpmyadmin.txt
@@ -81,6 +81,7 @@ owner:
Now point your web browser to `http://localhost/phpmyadmin`, and use
the MySQL user information to access the databases.
+.phpMyAdmin in action
image::media/images/cookbook_phpmyadmin.png[phpMyAdmin in action!]
Generic setup
@@ -138,4 +139,5 @@ Considerations
directory-type rules for those and manage them with the `HTTP Error`
handler.
+.Handler HTTP Error
image::media/images/cookbook_phpmyadmin_denied.png[Protected directories]
View
12 doc/cookbook_wordpress.txt
@@ -75,6 +75,7 @@ example.net
Remember to set up the `Document root` to `/var/www/wordpress`.
+.Custom document root
image::media/images/cookbook_wp_example1.png[WP example.net]
Delete all the rules except `php` and `Default`. We're heading right
@@ -83,12 +84,14 @@ to the second milestone now.
As previously, we will manage the `Default` rule with the redirection
handler.
+.Redirection handler
[cols="30%,30%,40%",options="header"]
|=====================================================
|Type | Regular Expression | Redirection
|Internal | ^/(.*)$ | /index.php
|=====================================================
+.Redirection handler
image::media/images/cookbook_wp_example2.png[WP example.net]
After this, most of the redirections will work. We'll set some more
@@ -118,9 +121,9 @@ Remeber to manage them with a handler that can serve files: `Static
content` and `List & Send`.
Almost any evaluation order of your rules will suffice, as long as the
-one that handles the PHP files is the first one. This is a valid one,
-for instance.
+one that handles the PHP files is the first one.
+.Rule list
image::media/images/cookbook_wp_example3.png[WP example.net]
@@ -185,23 +188,27 @@ quit;
Then point your web browser to `http://localhost` and follow the
instructions provided by the installer.
+.WordPress installation site info
image::media/images/cookbook_wp1.png[WP installation]
And the installation will be automatic. Just fill up the
requested values and you will obtain the following results once your
are through.
+.WordPress installation administrator info
image::media/images/cookbook_wp2.png[WP installation]
With that, you are done installing. Let's log in and make the last
adjustments.
+.WordPress login
image::media/images/cookbook_wp3.png[WP admin]
Once we're logged, we can configure the way `permalinks` are
displayed. Just use the `Settings`->`Permalinks` menu, and adjust the
way the links are to be rewritten.
+.Permalinks
image::media/images/cookbook_wp4.png[WP admin]
Remember to set up the plugins that are of interest for you, such as
@@ -211,6 +218,7 @@ configured in Cherokee.
And voilà! You have a WordPress installation working flawlessly with
Cherokee.
+.WordPress in action
image::media/images/cookbook_wp5.png[WP in action]
////////////////////////////////////////////////////////////////////////
Please sign in to comment.
Something went wrong with that request. Please try again.