[ic] need help with makecat

[Marco]

Hi to everyone,
I'm really trying hard to have Interchange 4.8.3 to work on my G4 
running mac os x 10.1.2. I've installed Perl 5.6.1 and CPAN version 
1.59 took care of downloading and installing successfully all the 
missing modules. I've also downloaded all the documentation available 
on Interchange and I've read Red Hat Getting Started Guide over and 
over; I still don't get it! How do you build and set up the catalog?
I have my root directory set up on /Library/WebServer/Documents and 
even if I have a /CGI-Executables directory, I run all my perl 
scripts in the root directory but with the .cgi extension.
I've installed Interchange in /Library/WebServer/Documents/ic and 
from there I ran the bin/makecat command. Now, in the following is a 
copy of the catalog configuration; no matter what I change, I cannot 
have the links to "customer entrance" and "admin interface" to work.
Can anyone help me?

Thank you

Marco Simonelli



Catalog name? foundation
makecat -- Interchange catalog installation program.

*** We will be making a catalog named 'foundation'. ***


Try using the UP arrow at some of the prompts -- you have the
Term::ReadLine module installed, and Interchange may find some
default values in your HTTP server configuration file.  You can
cycle among them with the UP and DOWN arrows.

######### BEGINNING CATALOG CONFIGURATION #########

During many of the following operations, defaults are placed in
a buffer for you. You may use the up and down arrows to toggle
between the defaults.

If you made a mistake on a *previous* entry and realize that
in a later one, if you enter ONLY an @ sign and press return you
should be returned to the previous step.

# The server name, something like: www.company.com
#                                  www.company.com:8000
#                                  www.company.com/~yourname
#
Server name? localhost

# The type of demo catalog to use. The standard one distributed is:
#
#    foundation
#
# If you have defined your own custom template catalog,
# you can enter its name.
#
# If you are new to Interchange, use "foundation" to start with.


DemoType? foundation

# The type of permission structure for multiple user catalogs.
# Select M for each user in own group (with interchange user in group)
#        G for all users in group of interchange user
#        U for all catalogs owned by interchange user (must be catuser as well)
#
#        M is recommended, G works for most installations.


permtype? M

# The user name the Interchange server runs under on this machine. This
# should not be the same as the user that runs the HTTP server (i.e.
# NOT nobody).
#


InterchangeUser? marco

#
# The user name the catalog will be owned by.
#


CatUser? marco

# The group name the server-owned files should be set to.  This is
# only important if Interchange catalogs will be owned by multiple users
# and the group to be used is not the default for the catalog user.
#
# Normally this is left blank unless G mode was selected above.
#


InterchangeGroup?

# The email address where orders for this catalog should go.
# To have a secure catalog, either this should be a local user name and
# not go over the Internet -- or use the PGP option.
#


MailOrderTo? marco@kc.rr.com

# Where the Interchange files for this catalog will go, pages,
# products, config and all.  This should not be in HTML document
# space! Usually a 'catalogs' directory below your home directory
# works well. Remember, you will want a test catalog and an online
# catalog.
#


CatRoot? /Users/marco/catalogs/foundation

# The location of the normal CGI directory. This is a
# file path, not a script alias.
#
# If all of your CGI programs must end in .cgi, this is
# should be the same as your HTML directory.
#


CgiDir? /Library/WebServer/Documents

# The URL location of the CGI program, without the http://
# or server name.
#
# http://www.virtual.com/cgi-bin/prog
#                       ^^^^^^^^^^^^^
#
# http://www.virtual.com/program.cgi
#                       ^^^^^^^^^^^^
#


CgiUrl?

#
# Additional URL locations for the CGI program, as with CgiUrl.
# This is used when calling the catalog from more than one place,
# perhaps because your secure server is not the same name as the
# non-secure one.
#
# http://www.secure.domain/secure-bin/prog
#                         ^^^^^^^^^^^^^^^^
#
# We set it to the name of the catalog by default to enable the
# internal HTTP server.
#


Aliases? /foundation

# The base directory for HTML for this (possibly virtual) domain.
# This is a directory path name, not a URL -- it is your HTML
# directory.
#


DocumentRoot? /Library/WebServer/Documents

# Where the sample HTML files (not Interchange pages) should be installed.
# There is a difference. Usually a subdirectory of your HTML directory.
#


SampleHtml? /Library/WebServer/Documents/ic

# Where the image files should be copied. A directory path
# name, not a URL.
#


ImageDir? /Library/WebServer/Documents/ic/images

# The URL base for the sample images. Sets the ImageDir
# directive in the catalog configuration file. This is a URL
# fragment, not a directory or file name.
#
#         <IMG SRC="/foundation/images/icon.gif">
#                   ^^^^^^^^^^^^^^^^^^
#


ImageUrl? /ic/images

Interchange can use either UNIX- or internet-domain sockets.
Most ISPs would prefer UNIX mode, and it is more secure.

If you already have a program there, or use a common program
and the FullURL directive, select NONE. You will then need
to copy the program by hand or otherwise ensure its presence.

(You can use the up/down arrows to toggle).
INET or UNIX mode? UNIX
Do you use CGIWRAP or SUEXEC? n
Checking directories........................................
/Users/marco/catalogs/foundation: directory exists!

/Library/WebServer/Documents/ic: directory exists!
The above directories already exist. Overwrite files? y
done.
Copying demo files..........................................found more to ask.

Your company name: ...............................Foundation Store

You can choose to pre-populate your Foundation template with some
data which might be illustrative. You can always delete it later
and replace it with your own.

The types are:

     tools      Construct Something, includes products, users, orders
     reports    Marketing reports, downloadable softgoods, products, users
     none       No data. Same as leaving blank.

Sample data type?: ...............................tools

Interchange has a workable internal database, but many things will
work better (and a few worse) if you use a SQL database. Interchange
can configure MySQL, PostgreSQL, and Oracle in a test configuration.

Set to 1 if you want to use MySQL, PostgreSQL, Oracle, or DB2: ..1

You can select this to use MySQL in your test catalog. Careful!
This requires the ability to create a database named "test_foundation",
and is highly dependent on your Perl and MySQL configuration. Don't
be too surprised if this doesn't work.

Set to 1 if you want to use MySQL: ...............1
Database to use (will be created): ...............test_foundation
DBI DSN to use: ..................................dbi:mysql:test_foundation
Username for MySQL (if any): .....................marco
Password for MySQL (if any): .....................passw

We can try and use mysqladmin to create the database in
MySQL. In many default MySQL distributions, any user can create
a database beginning with "test".

Use the next option to add parameters. If your MySQL is password-protected
(and you know the password) you may want to add "-u root -p".

Set to 1 to create 'test_foundation' with mysqladmin: ..1

To create the database you may need to supply a password and
username. To do that, add the option "-u USERNAME -p", where
USERNAME is a MySQL user with permission to create databases.
This is often the user "root".

Extra options for creation: ......................

You can use Interchange's companion configuration
interface, to do upload/download of files, manipulation of
the database, reconfiguration of the catalog, and much more.

To enable the UI, you will need a "super-user" account
name that has full access.

The initial password is "pass". CHANGE IT! You can do this
by going to the admin menu and selecting the superuser and
then "Change password".

Account name that will control this catalog: .....marco
Administrative password: .........................passw
Set to 1 to display demo helper features in your store: ..1

Found system commands to run.

Since you selected the MySQL option, you need to create a database named
"test_foundation". In a default MySQL configuration, any user may create
and drop and modify test_* databases, but some administrators disable this.

run "mysqladmin -u marco -plillo66 create test_foundation"? y
mysqladmin: CREATE DATABASE failed; error: 'Can't create database 
'test_foundation'. Database exists'

Command returned error code 1: No such file or directory
done.
Moving link program to /Library/WebServer/Documents/........done.
Copying share/ files to /Library/WebServer/Documents........done.
Moving HTML files to /Library/WebServer/Documents/ic........done.
Moving image files to /Library/WebServer/Documents/ic/images..done.

Found additional system commands to run.

We need to make some directories to store sessions, logs, and such.

run "sh /Users/marco/catalogs/foundation/config/makedirs"? y
You can install some sample data to start with in this catalog.
This script will install the sample (tools) you selected.

run "sh /Users/marco/catalogs/foundation/config/installsample"? y
Add catalog to interchange.cfg? y

Deleting old configuration foundation.

Done with installation. If my reading of your input is correct, you
should be able to access the demo catalog with the following URL:

         http://localhost/ic

In any case, you should get direct access at:

         http://localhost

That is, after you START or RESTART the Interchange server.  8-)
It is best done with:

         su -c "/Library/WebServer/Documents/ic/bin/interchange -r" marco

For session expiration, you might want to place a line like this in your
crontab:

44 4 * * * /Library/WebServer/Documents/ic/bin/expireall -r

It will prevent the session databases from getting too large.

[photomementos:Documents/ic/bin] root#

--