view release on metacpan or  search on metacpan

Docs/devmgr/devmgr.html  view on Meta::CPAN

1.10 of <tt>CVS</tt>.
<dt>
<b>CVSROOT</b></dt>

<dd>
Default: <tt>/opt/ims/repository</tt></dd>

<br>The <tt>cvs</tt> command relies on either a command-line specification
of a repository root, or for the value to be defined in an environment
variable named <b><tt>CVSROOT</tt></b>. Defining it here not only guarantees
consistency, but also prevents errors or data loss due to an incorrectly-set
value on the user end.
<dt>
<b>DEVHOST</b></dt>

<dd>
Default: <tt>webdev.nafohq.hp.com</tt></dd>

<br>The fully-qualified-domain name of the development host the tools are
running on. This is not currently used to any real extent, but was planned
for use by the <i>wrapper</i> component.
<dt>
<b>EVENT_LOG</b></dt>

<dd>
Default: <tt>/opt/ims/htdocs/development-log.txt</tt></dd>

<br>Many of the actions performed by the tools are check-pointed by an
entry written to this log as a single line. Not all tools are making maximum
use of this at present.
<dt>
<b>FTP</b></dt>

<dd>
Default: <tt>/opt/ims/bin/ftp</tt></dd>

<br>This is the full path to the <tt>ftp</tt> binary, defined for the same
reasons as the <tt>cvs</tt> binary. Additionally, this serves the purpose
of ensuring that the program used has been built with correct network library
code to allow it to pass through the firewall.
<dt>
<b>GROUP</b></dt>

<dd>
Default: <tt>idsweb</tt></dd>

<br>When files are created or updated in the project root or staging areas,
this value (which may also be expressed numerically) is used to set the
group ownership on such files and the directories that contain them.
<dt>
<b>HALTFILE_PREFIX</b></dt>

<dd>
Default: <tt>etc/halt-</tt></dd>

<br>This prefix is used when checking for "halt files" pertaining to the
command about to be run. Halt files are explained earlier. If the value
is not an absolute path, it is considered relative to the home directory
of the <b><tt>USER</tt></b> defined below.
<dt>
<b>HTTP_PROXY</b></dt>

<dd>
Default: <tt>http://web-proxy:8088</tt></dd>

<br>When the new-generation tools were being designed, <tt>HTTP</tt> file
upload was favored over <tt>FTP</tt>-based transmission, since the password
and user name were of less consequence if compromised. Due to limitations
related to the <tt>HTTP</tt>-based solution, this is gradually being phased
out and the original <tt>FTP</tt>-based approach is now preferred. This
parameter is used to define a proxy for the <tt>HTTP</tt> approach, if
one is needed. Without it, transfers beyond a firewall would not be possible.
<dt>
<b>OWNER</b></dt>

<dd>
Default: <tt>idsweb</tt></dd>

<br>This user name (or numeric ID if expressed as such) is used for several
purposes: it is the ownership assigned to files both in the <tt>CVS</tt>
repository and the staging areas, and it is the source for a home directory
to use as a base directory for the values <b><tt>HALTFILE_PREFIX</tt></b>
and <b><tt>ACL_DIR</tt></b>. It is also this user that is permitted to
override certain safeguards such as access-control lists and halt files.
<dt>
<b>PROJECT_ROOT</b></dt>

<dd>
Default: <tt>/opt/ims/htdocs</tt></dd>

<br>This is the area in which the developmental versions of project hierarchies
are kept. This is the designated document root for the server instance
that runs on the development host, and each project is kept in its own
unique directory under this root.
<dt>
<b>RELEASE</b></dt>

<dd>
Default: <tt>.release</tt></dd>

<br>The file which the <i>release</i>-specific tool updates to mark a successful
release. It is expected to be a simple file, not a path, and will be created/updated
in the project's directory under <b><tt>PROJECT_ROOT</tt></b>.
<dt>
<b>STAGE_ROOT</b></dt>

<dd>
Default: <tt>/opt/ims/staging</tt></dd>

<br>When a project is being staged in preparation for release to a different
host, the project directory is under this directory as its root. As explained
earlier, this directory fans out into a set of directories named for the
target external hosts, and the projects are staged under these host-specific
directories on a per-request basis. This allows for projects to be staged
to multiple hosts (i.e. a testing and a production machine) without concern
for conflicts in the staging area.
<dt>
<b>TAR</b></dt>

<dd>
Default: <tt>/opt/ims/bin/tar</tt></dd>