diff options
Diffstat (limited to 'data/doc/sisu/markup-samples/manual/en/sisu_commands.sst')
| -rw-r--r-- | data/doc/sisu/markup-samples/manual/en/sisu_commands.sst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_commands.sst b/data/doc/sisu/markup-samples/manual/en/sisu_commands.sst index 356f38e1..016ef7ea 100644 --- a/data/doc/sisu/markup-samples/manual/en/sisu_commands.sst +++ b/data/doc/sisu/markup-samples/manual/en/sisu_commands.sst @@ -286,7 +286,7 @@ see --qrcode see --quiet !_ --qrcode [filename/wildcard] \\ -generate QR code image of metadata (used in manifest). v3 only. +generate QR code image of metadata (used in manifest). !_ --quiet [filename/wildcard] \\ quiet less output to screen. @@ -315,8 +315,8 @@ see --sisupod !_ -s [filename/wildcard] \\ see --source -!_ --sample-search-form [--db=(pgsql|sqlite)] [--webserv=webrick] \\ -generate examples of (naive) cgi search form for SQLite or PgSQL depends on your already having used sisu to populate an SQLite or PgSQL database, (the SQLite version scans the output directories for existing sisu_sqlite databases, so it is first necessary to create them, before generating the search form) see --sqlite & --pg and the database section below. Optional additional parameters include: url location of webserver search form and db: --webserv-search='[url]'; location of webserver output: --webserv-output='[url]'; cgi search form link name: --cgi-search-form-name='[name.cgi]'; for pgsql, database user: --db-user='[username]'. If the optional parameter --webserv=webrick is passed, the cgi examples created will be set up to use the default port set for use by the webrick server, (otherwise the port is left blank and the system setting used, usually 80). The samples are dumped in the present work directory which must be writable, (with screen instructions given that they be copied to the cgi-bin directory). Alias -F +!_ --sample-search-form [--db-(pg|sqlite)] \\ +generate examples of (naive) cgi search form for SQLite or PgSQL depends on your already having used sisu to populate an SQLite or PgSQL database, (the SQLite version scans the output directories for existing sisu_sqlite databases, so it is first necessary to create them, before generating the search form) see --sqlite & --pg and the database section below. Optional additional parameters: --db-user='www-data'. The samples are dumped in the present work directory which must be writable, (with screen instructions given that they be copied to the cgi-bin directory). Alias -F !_ --scp [filename/wildcard] \\ copies sisu output files to remote host using scp. This requires that sisurc.yml has been provided with information on hostname and username, and that you have your "keys" and ssh agent in place. Also see --rsync. Alias -r @@ -484,7 +484,7 @@ The -v is for verbose output. Checks existing file output and runs the flags required to update this output. This means that if only html and pdf output was requested on previous runs, only the -hp files will be applied, and only these will be generated this time, together with the summary. This can be very convenient, if you offer different outputs of different files, and just want to do the same again. !_ -0 to -5 [filename or wildcard] \\ -Default shorthand mappings (for v3, note that the defaults can be changed/configured in the sisurc.yml file): +Default shorthand mappings (note that the defaults can be changed/configured in the sisurc.yml file): !_ -0 \\ -NQhewpotbxXyYv [this is the default action run when no options are give, i.e. on 'sisu [filename]'] |