view release on metacpan or  search on metacpan

lib/App/installguide.pod.ota  view on Meta::CPAN

#!perl -w
# run this document through perl to check its syntax
use Pod::Checker;
podchecker(\*DATA);
__END__

=head1 NAME

Business::Travel::OTA::installguide - Installation Guide for the Business-Travel-OTA Distribution

=head1 INTRODUCTION

This is the Installation Guide to the Business-Travel-OTA distribution
the Microsoft Windows platform.
You can find out more background to the project on the web.

  http://search.cpan.org/~spadkins/Business-Travel-OTA/lib/Business/Travel/OTA.pm
  http://search.cpan.org/~spadkins/Business-Travel-OTA
  http://sourceforge.net/projects/ota-tools
  http://www.opentravel.org 

This will describe how to get
up and running (for demonstration or development purposes) on a Unix/Linux system.

These instructions assume that your system is connected to the Internet.

=head1 SET UP THE ENVIRONMENT

You could just install all of the software into "/usr/local", or "/usr", or
wherever your Perl is installed.  In that case, skip this section.

If however, you are setting up a development environment, or
if you wish to install multiple versions of the App software,
it is advisable you choose an approach as follows.

=head2 Set Up a Development Environment

Choose a directory that will be the base of all App
environments (i.e. /usr/mycompany, any base directory will do).

  /usr/mycompany

Create a subdirectory for each separate developer/tester.
You may wish to choose groups rather than users (i.e. "devel", "qagroup").
(In this case, you would have several developers working in
one directory tree.  This may cause more conflicts between
developers during development, but the
conflicts get worked out more quickly than when developers
work in separate directories.)

  /usr/mycompany/spadkins
  /usr/mycompany/joe
  /usr/mycompany/marysue
  /usr/mycompany/devel
  /usr/mycompany/qagroup

These are independent development "sandboxes".
Later, when we start making releases of the software (which includes the App
framework), we will create other environment directories like this.

  /usr/mycompany/0.5.0
  /usr/mycompany/0.5.1
  /usr/mycompany/1.0.0
  /usr/mycompany/2.17.10

All of these directories will have their own self-contained installation
of software.  Named versions (i.e. "test", "qa", "prod") are simply
symbolic links to the particular version to which they currently apply.

In your chosen development directory, you should set the permissions
to allow access to be granted by group.

  chgrp -R spadkins /usr/mycompany/spadkins  # all files and dirs owned by group
  chmod 775 `find /usr/mycompany/spadkins -type d -print` # dirs writable by the group
  chmod g+s `find /usr/mycompany/spadkins -type d -print` # setgid bit keeps files in the group