diff options
Diffstat (limited to 'data/doc/manuals_generated/sisu_manual/sisu_remote/scroll.xhtml')
| -rw-r--r-- | data/doc/manuals_generated/sisu_manual/sisu_remote/scroll.xhtml | 262 |
1 files changed, 262 insertions, 0 deletions
diff --git a/data/doc/manuals_generated/sisu_manual/sisu_remote/scroll.xhtml b/data/doc/manuals_generated/sisu_manual/sisu_remote/scroll.xhtml new file mode 100644 index 00000000..1a80e3c9 --- /dev/null +++ b/data/doc/manuals_generated/sisu_manual/sisu_remote/scroll.xhtml @@ -0,0 +1,262 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<?xml-stylesheet type="text/css" href="../_sisu/css/xhtml.css"?> +<!-- Document processing information: + * Generated by: SiSU 0.59.0 of 2007w38/0 (2007-09-23) + * Ruby version: ruby 1.8.6 (2007-06-07 patchlevel 36) [i486-linux] + * + * Last Generated on: Sun Sep 23 04:12:20 +0100 2007 + * SiSU http://www.jus.uio.no/sisu +--> + +<document> +<head> + <meta http-equiv="Content-Type" content="text/html;charset=utf-8" /> + <meta>Title:</meta> + <title class="dc"> + SiSU - Remote Operations [0.58] + </title> + <br /> + <meta>Creator:</meta> + <creator class="dc"> + Ralph Amissah + </creator> + <br /> + <meta>Rights:</meta> + <rights class="dc"> + Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3 + </rights> + <br /> + <meta>Type:</meta> + <type class="dc"> + information + </type> + <br /> + <meta>Subject:</meta> + <subject class="dc"> + ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search + </subject> + <br /> + <meta>Date created:</meta> + <date_created class="extra"> + 2002-08-28 + </date_created> + <br /> + <meta>Date issued:</meta> + <date_issued class="extra"> + 2002-08-28 + </date_issued> + <br /> + <meta>Date available:</meta> + <date_available class="extra"> + 2002-08-28 + </date_available> + <br /> + <meta>Date modified:</meta> + <date_modified class="extra"> + 2007-09-16 + </date_modified> + <br /> + <meta>Date:</meta> + <date class="dc"> + 2007-09-16 + </date> + <br /> +</head> +<body> +<object id="1"> + <text class="h1"> + SiSU - Remote Operations [0.58],<br /> Ralph Amissah + </text> + <ocn>1</ocn> +</object> +<object id="2"> + <text class="h2"> + SiSU Remote Operations + </text> + <ocn>2</ocn> +</object> +<object id="3"> + <text class="h4"> + 1. Remote Source Documents + </text> + <ocn>3</ocn> +</object> +<object id="4"> + <text class="norm"> + <b>SiSU</b> processing instructions can be run against remote source +documents by providing the url of the documents against which the +processing instructions are to be carried out. The remote <b>SiSU</b> +documents can either be sisu marked up files in plaintext .sst or .ssm +or; zipped sisu files, sisupod.zip or filename.ssp + </text> + <ocn>4</ocn> +</object> +<object id="5"> + <text class="norm"> + <b>.sst / .ssm - sisu text files</b> + </text> + <ocn>5</ocn> +</object> +<object id="6"> + <text class="norm"> + <b>SiSU</b> can be run against source text files on a remote machine, +provide the processing instruction and the url. The source file and any +associated parts (such as images) will be downloaded and generated +locally. + </text> + <ocn>6</ocn> +</object> +<object id="7"> + <ocn>7</ocn> + <text class="code"> +    sisu -3 http://[provide url to valid .sst or .ssm file]     + </text> +</object> +<object id="8"> + <text class="norm"> + Any of the source documents in the sisu examples page can be used in +this way, see <<link xmlns:xlink="http://www.w3.org/1999/xlink" +xlink:type="simple" +xlink:href="http://www.jus.uio.no/sisu/SiSU/2.html">http://www.jus.uio.no/sisu/SiSU/2.html</link>> +and use the url for the desired document. + </text> + <ocn>8</ocn> +</object> +<object id="9"> + <text class="norm"> + NOTE: to set up a remote machine to serve <b>SiSU</b> documents in this +way, images should be in the directory relative to the document source +../_sisu/image + </text> + <ocn>9</ocn> +</object> +<object id="10"> + <text class="norm"> + <b>sisupod - zipped sisu files</b> + </text> + <ocn>10</ocn> +</object> +<object id="11"> + <text class="norm"> + A sisupod is the zipped content of a sisu marked up text or texts and +any other associated parts to the document such as images. + </text> + <ocn>11</ocn> +</object> +<object id="12"> + <text class="norm"> + <b>SiSU</b> can be run against a sisupod on a (local or) remote +machine, provide the processing instruction and the url, the sisupod +will be downloaded and the documents it contains generated locally. + </text> + <ocn>12</ocn> +</object> +<object id="13"> + <ocn>13</ocn> + <text class="code"> +    sisu -3 http://[provide url to valid sisupod.zip or .ssp file]     + </text> +</object> +<object id="14"> + <text class="norm"> + Any of the source documents in the sisu examples page can be used in +this way, see <<link xmlns:xlink="http://www.w3.org/1999/xlink" +xlink:type="simple" +xlink:href="http://www.jus.uio.no/sisu/SiSU/2.html">http://www.jus.uio.no/sisu/SiSU/2.html</link>> +and use the url for the desired document. + </text> + <ocn>14</ocn> +</object> +<object id="15"> + <text class="h3"> + Remote Document Output + </text> + <ocn>15</ocn> +</object> +<object id="16"> + <text class="h4"> + 2. Remote Output + </text> + <ocn>16</ocn> +</object> +<object id="17"> + <text class="norm"> + Once properly configured <b>SiSU</b> output can be automatically posted +once generated to a designated remote machine using either rsync, or +scp. + </text> + <ocn>17</ocn> +</object> +<object id="18"> + <text class="norm"> + In order to do this some ssh authentication agent and keychain or +similar tool will need to be configured. Once that is done the +placement on a remote host can be done seamlessly with the -r (for scp) +or -R (for rsync) flag, which may be used in conjunction with other +processing flags, e.g. + </text> + <ocn>18</ocn> +</object> +<object id="19"> + <ocn>19</ocn> + <text class="code"> +    sisu -3R sisu_remote.sst     + </text> +</object> +<object id="20"> + <text class="h5"> + 2.1 commands + </text> + <ocn>20</ocn> +</object> +<object id="21"> + <text class="norm"> + <b>-R [filename/wildcard] </b><br /> copies sisu output files to remote +host using rsync. 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. Note the behavior of rsync different if -R is used +with other flags from if used alone. Alone the rsync --delete parameter +is sent, useful for cleaning the remote directory (when -R is used +together with other flags, it is not). Also see -r + </text> + <ocn>21</ocn> +</object> +<object id="22"> + <text class="norm"> + <b>-r [filename/wildcard] </b><br /> 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 -R + </text> + <ocn>22</ocn> +</object> +<object id="23"> + <text class="h5"> + 2.2 configuration + </text> + <ocn>23</ocn> +</object> +<object id="24"> + <text class="norm"> + [expand on the setting up of an ssh-agent / keychain] + </text> + <ocn>24</ocn> +</object> +<object id="25"> + <text class="h4"> + 3. Remote Servers + </text> + <ocn>25</ocn> +</object> +<object id="26"> + <text class="norm"> + As <b>SiSU</b> is generally operated using the command line, and works +within a Unix type environment, <b>SiSU</b> the program and all +documents can just as easily be on a remote server, to which you are +logged on using a terminal, and commands and operations would be pretty +much the same as they would be on your local machine. + </text> + <ocn>26</ocn> +</object> +</body> +</document> |