/ 
OpenInteract-1.99_01
River stage zero No dependents
/ oi2_manage

NAME

oi2_manage - Command-line interface to OpenInteract management tasks

SYNOPSIS

oi2_manage [task] [options]

To see all tasks:

oi2_manage list_tasks

Common options:

--website_dir  - Directory of website
--source_dir   - Directory of OI2 source (at least pkg/ and sample/ dirs)
--package      - One or more packages to operate on
--package_dir  - Directory for package
--package_file - Package distribution file (eg, 'base_page-2.51.zip')
--status       - View more numerous status messages instead of progress messages
--debug        - Turn debugging on

Example: Install a website:

$ cd /opt/OpenInteract-2.05
$ oi2_manage create_website --website_dir=/home/httpd/mysite

Example: Install a package to a website using OPENINTERACT2 env instead of --website_dir:

$ export OPENINTERACT2=/home/httpd/mysite
$ oi2_manage install_package --package_file=/path/to/mypackage_1.00.zip

Example: Export a package

$ cd /path/to/my/package
$ oi2_manage export_package

Example: Check a package

$ cd /path/to/my/package
$ oi2_manage check_package

Example: Create the skeleton for a new package

$ cd /path/to/my/workdir
$ oi2_manage create_package --package=foopkg --source_dir=/opt/OpenInteract-2.05

DESCRIPTION

This is the command-line interface to the OpenInteract2::Manage module and all of its associated tasks. Since this is a simple shell around the management tasks it doesn't list all the tasks. (The docs here and the tasks would soon get out of sync.) Instead, just run:

oi2_manage list_tasks

And you'll get a list of tasks with a brief description for each. Guaranteed to be up-to-date.

You can find the optional and required parameters for a particular task with:

oi2_manage task_info --task=create_website

BUGS

None known.

TO DO

Nothing known.

SEE ALSO

OpenInteract2::Manage

COPYRIGHT

Copyright (c) 2002 intes.net, inc.. All rights reserved.

This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

AUTHORS

Chris Winters <chris@cwinters.com>