diff options
Diffstat (limited to 'data/doc/manuals_generated/sisu_manual/sisu_remote/dom.xml')
| -rw-r--r-- | data/doc/manuals_generated/sisu_manual/sisu_remote/dom.xml | 411 |
1 files changed, 411 insertions, 0 deletions
diff --git a/data/doc/manuals_generated/sisu_manual/sisu_remote/dom.xml b/data/doc/manuals_generated/sisu_manual/sisu_remote/dom.xml new file mode 100644 index 00000000..a372d89f --- /dev/null +++ b/data/doc/manuals_generated/sisu_manual/sisu_remote/dom.xml @@ -0,0 +1,411 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<?xml-stylesheet type="text/css" href="../_sisu/css/dom.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:12 +0100 2007 + * SiSU http://www.jus.uio.no/sisu +--> + +<document> + +<head> + + <header> + <meta>Title:</meta> + <title> + SiSU - Remote Operations [0.58] + </title> + </header> + + <header> + <meta>Creator:</meta> + <creator> + Ralph Amissah + </creator> + </header> + + <header> + <meta>Rights:</meta> + <rights> + Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3 + </rights> + </header> + + <header> + <meta>Type:</meta> + <type> + information + </type> + </header> + + <header> + <meta>Subject:</meta> + <subject> + ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search + </subject> + </header> + + <header> + <meta>Date created:</meta> + <date_created> + 2002-08-28 + </date_created> + </header> + + <header> + <meta>Date issued:</meta> + <date_issued> + 2002-08-28 + </date_issued> + </header> + + <header> + <meta>Date available:</meta> + <date_available> + 2002-08-28 + </date_available> + </header> + + <header> + <meta>Date modified:</meta> + <date_modified> + 2007-09-16 + </date_modified> + </header> + + <header> + <meta>Date:</meta> + <date> + 2007-09-16 + </date> + </header> + + + + + + +</head> + +<body> + +<heading1> + <heading> + <object id="1"> + <ocn>1</ocn> + <text>SiSU - Remote Operations [0.58],<br /> Ralph Amissah</text> + </object> + </heading> + + <heading2> + <heading> + <object id="2"> + <ocn>2</ocn> + <text>SiSU Remote Operations</text> + </object> + </heading> + + <contents1> + <heading> + <object id="3"> + <ocn>3</ocn> + <nametag>remote_source</nametag> + + <text>1. Remote Source Documents </text> + </object> + </heading> + <content> + + <object id="4"> + + + <ocn>4</ocn> + + + <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> + + </object> + + + <object id="5"> + + + <ocn>5</ocn> + + + <text class="norm"><b>.sst / .ssm - sisu text files</b></text> + + </object> + + + <object id="6"> + + + <ocn>6</ocn> + + + <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> + + </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"> + + + <ocn>8</ocn> + + + <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> + + </object> + + + <object id="9"> + + + <ocn>9</ocn> + + + <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> + + </object> + + + <object id="10"> + + + <ocn>10</ocn> + + + <text class="norm"><b>sisupod - zipped sisu files</b></text> + + </object> + + + <object id="11"> + + + <ocn>11</ocn> + + + <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> + + </object> + + + <object id="12"> + + + <ocn>12</ocn> + + + <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> + + </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"> + + + <ocn>14</ocn> + + + <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> + + </object> + + + </content> + + </contents1> + + <heading3> + <heading> + <object id="15"> + <ocn>15</ocn> + <text>Remote Document Output</text> + </object> + </heading> + + <contents1> + <heading> + <object id="16"> + <ocn>16</ocn> + <nametag>remote_output</nametag> + + <text>2. Remote Output </text> + </object> + </heading> + <content> + + <object id="17"> + + + <ocn>17</ocn> + + + <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> + + </object> + + + <object id="18"> + + + <ocn>18</ocn> + + + <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> + + </object> + + + <object id="19"> + + + <ocn>19</ocn> + + + <text class="code"> + +    sisu -3R sisu_remote.sst     + + </text> + + </object> + + + </content> + + <contents2> + <heading> + <object id="20"> + <ocn>20</ocn> + <nametag>2.1</nametag> + + <text>2.1 commands</text> + </object> + </heading> + <content> + + <object id="21"> + + + <ocn>21</ocn> + + + <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> + + </object> + + + <object id="22"> + + + <ocn>22</ocn> + + + <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> + + </object> + + + </content> + + </contents2> + + <contents2> + <heading> + <object id="23"> + <ocn>23</ocn> + <nametag>2.2</nametag> + + <text>2.2 configuration</text> + </object> + </heading> + <content> + + <object id="24"> + + + <ocn>24</ocn> + + + <text class="norm">[expand on the setting up of an ssh-agent / keychain]</text> + + </object> + + + </content> + + </contents2> + + </contents1> + + <contents1> + <heading> + <object id="25"> + <ocn>25</ocn> + <nametag>remote_servers</nametag> + + <text>3. Remote Servers </text> + </object> + </heading> + <content> + + <object id="26"> + + + <ocn>26</ocn> + + + <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> + + </object> + + + </content> + </contents1> + + </heading3> + + </heading2> + +</heading1> + +</body> + +</document> + |