File:
[LON-CAPA] /
loncom /
build /
install_web_site_cronjob
Revision
1.6:
download - view:
text,
annotated -
select for diffs
Mon Feb 3 18:03:52 2003 UTC (21 years, 11 months ago) by
harris41
Branches:
MAIN
CVS tags:
version_1_1_X,
version_1_1_99_1,
version_1_1_99_0,
version_1_1_3,
version_1_1_2,
version_1_1_1,
version_1_1_0,
version_1_0_99_3,
version_1_0_99_2,
version_1_0_99_1,
version_1_0_99,
version_1_0_3,
version_1_0_2,
version_1_0_1,
version_1_0_0,
version_0_99_5,
version_0_99_4,
version_0_99_3,
version_0_99_2,
version_0_99_1,
version_0_99_0,
conference_2003,
HEAD
best wishes to all.
#!/usr/bin/perl
=pod
=head1 NAME
install_web_site_cronjob - maintain install.lon-capa.org web-site every day
=head1 DESCRIPTION
This is a file that runs periodically on B<install.lon-capa.org>.
This file should be run by the 'loninst' user and be part of
the 'loninst' crontab entries (to view loninst crontab, login
as loninst and crontab C<-l>; to edit loninst crontab, login as
loninst and crontab C<-e>).
This file should be on the B<install.lon-capa.org> filesystem as
F</home/loninst/auto/install_web_site_cronjob>.
The current 'loninst' crontab entry is:
13 16 * * * /home/loninst/auto/install_web_site_cronjob
The main goal of B<install_web_site_cronjob> is to periodically produce the
unstable tarball needed for LON-CAPA installation.
A secondary yet important function of B<install_web_site_cronjob> is that it
also refreshes the documentation present on the install.lon-capa.org
web site.
This documentation is refreshed based on a file located inside
F</home/loninst/public_html/versions>. This file is named
F<LATEST-IS-VERSIONNUMBER>, where
I<VERSIONNUMBER> is the latest stable release of loncapa (e.g. 0.4 or 0.6.1).
The F<LATEST-IS-VERSIONNUMBER> file contains a string
that is used to date the release of the current stable version.
The coding of this script is a strange brew of shell commands
with perl.
=head1 AUTHOR
=cut
# --------------------------------------------- Making the tarball distribution
# In an ideal world, this tarball distribution would be always generated with
# the "make tardist" command. But instead, unstable is now defined as
# "all the gunk we have been working on", whereas the
# "make tardist" command means a "carefully inventoried selection of gunk".
#`cd /home/loninst/auto; export CVS_PASSFILE=/home/loninst/.cvspass; export CVSROOT=:pserver:scott\@localhost:/home/cvs; rm -Rf loncapa/[C][^V]*; rm -Rf loncapa/[^C]*; cvs -Q co loncapa; cd loncapa/loncom/build; make build 2>/dev/null; make tardist;`;
# The real world. Just give them all the gunk for the unstable distribution.
`cd /home/loninst/auto; export CVS_PASSFILE=/home/loninst/.cvspass; export CVSROOT=:pserver:scott\@localhost:/home/cvs; rm -Rf loncapa-unstable; rm -Rf loncapa; cvs -Q export -r HEAD loncapa;`;
# Generate a README file that advises them about dealing with the gunk.
open(OUT,'>/home/loninst/auto/loncapa/README');
print(OUT <<END);
This is a CVS export of LON-CAPA generated on:
END
print(OUT `date`);
print(OUT <<END);
To generate an installable tarball distribution from this file, you can
execute the following commands:
cd loncom/build
make tardist
Note that the installable tarball distribution (the 'tardist' target)
is what encapsulates the stable releases of the LON-CAPA software (as
well as ensuring that LON-CAPA's distributability does not rely solely on
CVS software).
END
print(OUT <<END);
An alternative Makefile command sequence is:
cd loncom/build
make build
make install
For more information on Makefile targets, you can just enter the following
commands:
cd loncom/build
make help
Finally, if you encounter any problems, be sure to enter them
into the bug database http://bugs.lon-capa.org/ or, alternatively,
discuss them on one of the mailing lists available at
http://mail.lon-capa.org/.
END
close(OUT);
# Roll the directory together into the unstable tarball.
`cd /home/loninst/auto; ln -s loncapa loncapa-unstable; tar cvvf loncapa-unstable.tar loncapa-unstable/* ;gzip -9 -f loncapa-unstable.tar`;
# ---------------------------------------- Dynamically generating documentation
`cd /home/loninst/auto/loncapa/loncom/build; make pdfdoc`;
`cd /home/loninst/auto/loncapa/loncom/build; make doc`;
`cd /home/loninst/auto/loncapa/loncom/build; cp docs.tar.gz /home/loninst/public_html/docs/.`;
`cd /home/loninst/public_html/docs; tar xzf docs.tar.gz`;
# ------------------------------------ Copying over the latest unstable tarball
#my $filename=`cd /home/loninst/auto; find loncapa -type f -name *.tar.gz -maxdepth 1`;
#chomp($filename);
#$filename=~/loncapa\/loncapa\-(.*?)\.tar\.gz/;
#my $version=$1;
`cd /home/loninst/auto; cp -f loncapa-unstable.tar.gz ../public_html/versions/loncapa-unstable.tar.gz`;
#`cd /home/loninst/public_html/versions; rm -f loncapa-unstable.tar.gz; ln -s loncapa-$version-unstable.tar.gz loncapa-unstable.tar.gz`;
# ------------------------------------------------ Determine the latest version
my $filename=`cd /home/loninst/public_html/versions; find . -type f -name LATEST-IS-* -maxdepth 1`;
chomp($filename);
$filename =~ /LATEST-IS-(.*)/;
my $version = $1;
open(IN,"</home/loninst/public_html/versions/$filename");
my $releasedate = <IN>;
close(IN);
# ------------------ Updating the download page with the date of the last build
open(IN,"</home/loninst/public_html/docs/downloads/index.html");
my @lines = <IN>;
close(IN);
my $date = `date -I`; chomp($date);
my $text = join('',@lines);
$text =~ s/loncapa-unstable\.tar\.gz\<\/a\>.*?\./loncapa-unstable\.tar\.gz\<\/a\> (generated $date)\./;
$text =~ s/LATESTVERSION/$version/g;
$text =~ s/LATESTDATE/$releasedate/g;
open(OUT,">/home/loninst/public_html/docs/downloads/index.html");
print(OUT $text);
close(OUT);
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>