README 1st - QUICK SETUP for FutureSQL
============================================================================

The directory structure in this file is as follows:

1. 'typical_home_directory' is whatever YOUR website's home directory is.
   That is, don't make a directory called 'typical_home_directory' -
   instead, place the 'futuresql' subdir inside your home directory.

2. The directory 'www' should NOT be created, but instead, represents
   YOUR website's 'web document root', often called 'www' or 'HTML' or
   'public_html' or 'htdocs'. Place the files and directory inside 'www'
   into YOUR web document root.

3. Adjust the paths in 'futuresql.cgi' and 'fsql_site_db.pl'
   accordingly.

   Also edit the VARIABLES in fsql_site_db.pl and fsql_setup.pl,
   including the methods and values in the connect_to_db
   subroutine.

4. Under Unix, make sure the 'futuresql.cgi' file is set to
   755 or 'rwxr-xr-x'.
   
   Set fsql_make.cgi to 700 or 'rwx------'.
   Set .my.cnf to 600 or 'rw-------'.
	 
   The other files can all be 644 or 'rw-r--r--'.

   ONLY futuresql.cgi needs to be within the
   web document root. The other files SHOULD BE OUTSIDE of
   the web document root -- NOT visible from the web.

5. The 'backup' dir should be '777' or 'rwx-rwx-rwx', because
   files created will be owned by the web server, usually
   'nobody'. This is why this method is only for quick backups,
   since you don't want your backup files read by everyone.

   This backup dir is for the backups done from the Administration
   Menu. You should use a different dir when you backup your files
   with MySQL Backup (see worldcommunity.com.)

6. The 'sessions' directory should be outside of the web tree,
   and should be set to 777.

7. Of course, you have to create your MySQL tables, and setup your
   permissions in the MySQL permissions tables.

8. Edit the .my.cnf and .www.my.cnf files based on #6.

9. Run 'fsql_make.cgi' AFTER you've created your MySQL tables; it
   will then create a dictionary file and 7 html templates which
   you'll need to MOVE to the correct directories. (I make my
   files in a 'work' directory.)

   To load the books demo tables run the script:
   load.book.tables.sh. You may have to edit and move
   the files depending upon your hosting situation.
   The files load a few default 'demo' records.

10. You'll typically want to add 'popup_menu' values to the
    dictionary files, based on arrays and hashes you setup in
    the 'fsql_dictionary_vars.pl' file. (see the books demo
    for examples of this.)

11. Make sure all files are uploaded as 'text' (if they're text)
    and 'binary' if they're graphics. This can affect how
    the perl scripts run.

--- Check out the other docs and SCRIPT COMMENTS as well, of course.

============