I noticed that there are differences between the modules. There are some that: * Are empty (phispy) * Are one line and difficult to read (genopheno) * Try to download a file instead of displaying content (sr) * Are much more elaborate and complete than others (http://140.221.85.77/command-docs/pe/coex_cluster.txt vs http://140.221.85.77/command-docs/genome_annotation/a_and_b.txt) It is going to be difficult for a script to compensate for all the variation. Otherwise, good place to start. Miriam From: Michael Sneddon <[email protected]<mailto:[email protected]>> Date: Tuesday, May 21, 2013 2:06 PM To: Tom Brettin <[email protected]<mailto:[email protected]>>, Elizabeth Glass <[email protected]<mailto:[email protected]>> Cc: Keith Keller <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [Release-team] auto generation of command -h output During this last build meeting, Keith and I put together, using some of Bob's invocation code, a method for capturing the help output of the command-line scripts which service owners have declared using the COMMANDS file. I put up an example of the output here: http://140.221.85.77/command-docs/ The commands are grouped into folders which are named with the "group-name" declared in the COMMANDS files. In each of these folders, there is an 'index.txt' file which includes the verbose name of the set of commands on the first line, followed by a list of all the commands that were declared. For each of these commands, there is a text file in the folder with the actual commands '-h' help output. If the text file for a command is empty, then for some reason the script with the '-h' option did not run successfully or no help was printed. Let me know if you have questions. The format of this output is fairly easy to change. For those on the release team, this help output generation can be invoked from the invocation service Makefile with the "deploy-command-docs" target. This output is placed in /kb/deployment/services/invocation/webroot/. Perhaps we should start including this step by default whenever the invocation service is deployed? -michael