view release on metacpan or  search on metacpan

Docs/install/RelMgrClientInstall.html  view on Meta::CPAN

<UL>
<LI>~idsweb/etc/acl</FONT><FONT SIZE=2> directory</LI></UL>
</UL>

<LI>Future:</LI> 
<UL>

<UL>
<FONT SIZE=2><LI>the </FONT><FONT FACE="Courier New" SIZE=2>acl</FONT><FONT SIZE=2> (access control list) directory is specified in the global config file at </FONT><FONT FACE="Courier New" SIZE=2>/opt/ims/local/dev_release.cfg</LI>
</FONT><FONT SIZE=2><LI>the </FONT><FONT FACE="Courier New" SIZE=2>acl</FONT><FONT SIZE=2> directory should be relocated to some common nfs mounted location such as </FONT><FONT FACE="Courier New" SIZE=2>/opt/ims/local/acl</LI></UL>
</UL>


</FONT></OL>


<B><I><FONT FACE="Arial"><P>Adding Mirror Specifications and Host Lists to Oracle</P>
</B></I></FONT><FONT SIZE=2><P>There is now a tool for editing the mirror specification database. It operates on a CGI/HTTP model, and is as secure as can be without using SSL directly. A manual page for the tool is part of the </FONT><FONT FACE="Cou...
</HTML>

rlsmgr/deploy_content  view on Meta::CPAN

deploy_content [ B<-t> I<num> ] [ B<-T> I<file> ] [ B<-c> I<file> ] mirror_group file

=head1 DESCRIPTION

The B<deploy_content> application is the second stage on the server-side of
the release manager process. It is generally called by B<rlsmgrd> when there
is a package in the incoming area that requires deployment.

The role of this tool is to validate the new package file, verify the
checksum, dissolve the archive into a staging area, and invoke the third-stage
tool to manage the relocation of data from the staging area to the actual
web server directories.

=head1 OPTIONS

B<deploy_content> requires that a I<mirror group> be specified on the 
command-line. This group name uniquely identifies a group of one or more
servers that handle a given externally-visible hostname. Following this, there
needs to be the name of the info file for the package being processed. This
will be sought in either the incoming or staging directories (which are
defined in the mirror group specification). In addition to these required

rlsmgr/process_content  view on Meta::CPAN

process_content - Manage the tasks of moving files from the staging area to the server area

=head1 SYNOPSIS

process_content [ B<-t> I<num> ] [ B<-T> I<file> ] [ B<-c> I<file> ] mirror_group

=head1 DESCRIPTION

B<process_content> is the third of three stages that run on the server end
of the release manager. It is used to relocate files from the staging area
into the web server content areas, doing some minimal adjustment to CGI
paths in the process (the majority of path normalization should be done at
packaging time, on the client side).

Though the B<process_content> tool reads from the same mirror specification
as the other two stages, it uses a minimal amount of data from external
sources. It expects to be invoked within the directory that is to be
processed; the listing file (usually called C<weblist> or C<Weblist>) is
expected to be in the current working directory, and all files referred to
within are taken to be relative paths.