mysql> CREATE DATABASE guide_on_the_side;

  mysql> GRANT ALL ON guide_on_the_side.*
           TO gots_user@localhost IDENTIFIED BY 'my_password';

  database:
   datasource: Database/Mysql
   host: localhost
   login: gots_user
   password: my_password
   database: guide_on_the_side

If you're not using an external SMTP server, set `transport` to `php` and leave the `smtp` section blank.

 Alternatively, there is an SQL schema available in app/Config/Migration/sql/install.sql.

8. Change permissions of app/tmp to make it and all sub-folders writable by
 the web server. Example command (for Unix-like systems):

chmod -R 777 app/tmp

 You're encouraged to make the permissions more restrictive than this example.

9. Change permissions of app/webroot/uploads to make it and all sub-folders writable by
 the web server. Example command (for Unix-like systems):

chmod -R 777 app/webroot/uploads

 You're encouraged to make the permissions more restrictive than this example.

10. If all went as planned, the public interface should now be available at
 http://your.domain/guide_on_the_side/ (assuming the folder you unzipped to
 in step 1 was in your server web root.)
11. You may log in at http://your.domain/guide_on_the_side/login to begin creating
 tutorials. The default username / password is:

  admin / GuideOnTheSideAdmin#1

 You should change this immediately and, ideally, add some non-admin
 accounts!

Installation procedure (if you want to clone from GitHub)
-------------------------------------------------------------------------------
If you'd prefer to get Guide on the Side by cloning directly from GitHub, there
are a couple extra steps. Note that the pre-built package from
code.library.arizona.edu does come as a git clone, so you can still upgrade by
pulling from GitHub if you install that way.

1. Clone Guide on the Side from GitHub into the appropriate folder on your web
 server. Example command:

2. Check out the latest tag. To see a list of tags, run git tag. Example
 command:

3. CakePHP is not included in our GitHub repository, so download it and place
 the lib folder into your Guide on the Side root. CakePHP 2.6.x is known to
 work. Example command:

4. Now follow the pre-built package instructions starting at step 2.

User Feedback
-------------
At the end of each tutorial, Guide on the Side gives users the ability to give feedback by displaying a link that reads "What did you think of this tutorial?".  When clicked, the link will open a modal popup that will allow the user to send feedback to the tutorial's creator.  The text of this link can be changed and the link itself can be suppressed entirely by editing the `feeback_link` section of config.yml, e.g.

External Authentication Services (CAS, Shibboleth)
--------------------------------------------------
By default, Guide on the Side uses a local authentication system, but it can be easily configured to use CAS or Shibboleth instead.

To use an external authentication service, open config.yml in a text editor and find the `authentication` section.  Change `method` to the appropriate value for your authentication service and add the correct configuration options to the corresponding section.  For example, to enable Shibboleth, you'd want to do something like this:

Support and Debugging
---------------------
If you run into problems, check out the Guide on the Side discussion at:

    https://groups.google.com/forum/#!forum/gots-discuss

and the issues list at:

    https://github.com/ualibraries/Guide-on-the-Side/issues

If you get errors *after* installation, in addition to checking the Apache error
log also look at the messages in the Guide on the Side error log:

    ./guide_on_the_side/app/tmp/logs/error.log

Customization
-------------------------------------------------------------------------------
Guide on the Side is an open-source application and, obviously, you have full
permission to change it however you want.

But you shouldn't.

Or, at least, you shouldn't without realizing what you're getting into. If you
change the application simply because you want to add institutional branding, say, or
you just don't like the colors, there is a better way -- better for you, that
is.

It can be extremely difficult for a customized (also called "forked")
open-source product to take advantage of updates to the original application.
And it's entirely likely that you'll want to take advantage of any future
updates to Guide on the Side. There are very good reasons for customization /
forking, of course, but if you don't already know what those are, please read
on for a way that you can have control over the presentation of Guide on the
Side without losing the advantage of receiving upgraded functionality in the
future.

Because Guide on the Side is built using the CakePHP framework, it includes
some basic theming ability. At this time, it is possible to change any
part of the interface using this theming functionality included with this
framework. In other words, using themes you can change how the
application *looks*, but not *what it does*.

The short version: you can create a new folder inside of
guide_on_the_side/themes/Themed, and then in config.yml enter the name of this
new folder as the value for the theme parameter (e.g., "theme: UAL"). Any file
that you find inside of app/View or app/webroot can now be overridden by
placing an identically named file inside your new theme. For example, if
you'd like to override the main public index of Guide on the Side, copy
app/View/Tutorials/search.ctp into
themes/Themed/[your_theme]/Tutorials/search.ctp and then modify as you
wish. (See app/Config/routes.php for a list of non-obvious routes.)

For more information, see the Themes portion of the CakePHP book:
http://book.cakephp.org/2.0/en/views/themes.html

Credits
-------------------------------------------------------------------------------
Close, print, dock/undock icons:
 - Authored by Mark James - http://famfamfam.com/lab/icons/silk/
 - Used under CC BY 3.0 license - http://creativecommons.org/licenses/by/3.0/

Copyright (C) 2011-2015 The Arizona Board of Regents on Behalf of the
University of Arizona. Developed by Leslie Sult, Justin Spargur,
Mike Hagedon, Ginger Bidwell, Gabriel Luethje, and Will Simpson at the 
University of Arizona Libraries.