Review (NS-136): Added RunNetarchiveSuite.sh to scripts and updated it so that...

Author

Henrik Kirk

Moderator

Henrik Kirk

State

Closed

Objectives

1211: Added RunNetarchiveSuite.sh to scripts and updated it so that is display usage, if used wrong.

Summary

Time Use:
JOLF: 0.2
HBK: 0.1

General comments:

Description

Classification

Status

Comments on file 'trunk/scripts/RunNetarchiveSuite.sh', revision 1211

Lines

Description

Classification

Status

General

This is basically the script from the Installation manual. Since it is part of trunk it only will be accessible when the NetarchiveSuite-*.zip has been unzipped. Thus, when running this script along with a 'deploy_standalone' configuration file, the NetarchiveSuite-*.zip will be unzipped at the installation folder at 'USER'. Then the install script will be run, which will unzip the NetarchiveSuite-*.zip on the same machine a third time. It should be possible to replace step 4, so it does not unzip NetarchiveSuite-*.zip before running Deploy. It should be possible to find the 'basedir' by looking for the 'lib' directory or one of the libraries within. This will render the argument 'USER' superfluous. Also, it should be possible to replace the 'installation directory' within the deploy file with the current 'basedir'. This means that you would have the 'install_local', 'start_local' and 'kill_local' scripts in the 'basedir' and all the 'settings', 'start_app', 'kill_app', etc. in the 'conf' directory. Though the replacement of the installation directory should only occur if the machine is localhost. This will save space (each unzipped NetarchiveSuite takes up around 50 mb) and potential confusion over where to find the real installation. MAKE FR!

Minor

OK

9

Perhaps write that 'USER' is the output directory. And describe the others as well.

Cosmetic

OK

16

Comments should be deleted

Cosmetic

OK

IssuesFromNs136 (last edited 2010-08-16 10:24:38 by localhost)