ELOG/elog
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
d2a64a50711bd42e2caf073230974a9463d410aa
elog/mkdocs/site/userguide/index.html
T
ritt a17089c1c7 Added MkDocs files
2025-10-02 10:36:57 +02:00

565 lines
29 KiB
HTML
Raw Blame History

<!DOCTYPE html>
<html class="writer-html5" lang="en" >
<head>
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<link rel="shortcut icon" href="../img/favicon.ico" />
<title>User guide - ELOG Electronic Logbook</title>
<link rel="stylesheet" href="../css/theme.css" />
<link rel="stylesheet" href="../css/theme_extra.css" />
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.8.0/styles/github.min.css" />
<script>
// Current page data
var mkdocs_page_name = "User guide";
var mkdocs_page_input_path = "userguide.md";
var mkdocs_page_url = null;
</script>
<!--[if lt IE 9]>
<script src="../js/html5shiv.min.js"></script>
<![endif]-->
<script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.8.0/highlight.min.js"></script>
<script>hljs.highlightAll();</script>
</head>
<body class="wy-body-for-nav" role="document">
<div class="wy-grid-for-nav">
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
<div class="wy-side-scroll">
<div class="wy-side-nav-search">
<a href=".." class="icon icon-home"> ELOG Electronic Logbook
</a><div role="search">
<form id ="rtd-search-form" class="wy-form" action="../search.html" method="get">
<input type="text" name="q" placeholder="Search docs" aria-label="Search docs" title="Type search term here" />
</form>
</div>
</div>
<div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="Navigation menu">
<ul>
<li class="toctree-l1"><a class="reference internal" href="..">Home</a>
</li>
</ul>
<ul class="current">
<li class="toctree-l1 current"><a class="reference internal current" href="#">User guide</a>
<ul class="current">
<li class="toctree-l2"><a class="reference internal" href="#a-quick-intro">A Quick Intro</a>
</li>
<li class="toctree-l2"><a class="reference internal" href="#what-words-mean-here">What Words Mean Here</a>
</li>
<li class="toctree-l2"><a class="reference internal" href="#accessing-an-elog-server-and-its-logbooks">Accessing an ELOG server and its logbook(s)</a>
</li>
<li class="toctree-l2"><a class="reference internal" href="#viewing-information-in-elog">Viewing information in ELOG</a>
</li>
<li class="toctree-l2"><a class="reference internal" href="#browsing-around-and-finding-things">Browsing around and finding things</a>
</li>
<li class="toctree-l2"><a class="reference internal" href="#adding-stuff-to-a-logbook">Adding stuff to a logbook</a>
</li>
<li class="toctree-l2"><a class="reference internal" href="#misc-tips-tricks-things-to-be-aware-of">Misc. tips &amp; tricks, things to be aware of...</a>
</li>
<li class="toctree-l2"><a class="reference internal" href="#elog-command-line-client">elog command line client</a>
</li>
<li class="toctree-l2"><a class="reference internal" href="#rss-feed">RSS Feed</a>
</li>
</ul>
</li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../adminguide/">Admin guide</a>
</li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../config/">Config file</a>
</li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../faq/">FAQ</a>
</li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../forum/">Forum</a>
</li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../wishlist/">Wishlist</a>
</li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../contrib/">Contributions</a>
</li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../demo/">Demo</a>
</li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../download/">Download</a>
</li>
</ul>
</div>
</div>
</nav>
<section data-toggle="wy-nav-shift" class="wy-nav-content-wrap">
<nav class="wy-nav-top" role="navigation" aria-label="Mobile navigation menu">
<i data-toggle="wy-nav-top" class="fa fa-bars"></i>
<a href="..">ELOG Electronic Logbook</a>
</nav>
<div class="wy-nav-content">
<div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
<ul class="wy-breadcrumbs">
<li><a href=".." class="icon icon-home" aria-label="Docs"></a></li>
<li class="breadcrumb-item active">User guide</li>
<li class="wy-breadcrumbs-aside">
</li>
</ul>
<hr/>
</div>
<div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
<div class="section" itemprop="articleBody">
<h1 id="elog-users-guide">ELOG User's Guide</h1>
<p><em>How to get the most from your ELOG server</em></p>
<hr />
<h2 id="a-quick-intro">A Quick Intro</h2>
<p><strong>ELOG</strong> is part of a family of applications known as <em>weblogs</em>. Their
general purpose is :</p>
<ol>
<li>to make it easy for people to put information online in a
chronological fashion, in the form of short, time-stamped text
messages ("<em>entries</em>") with optional HTML markup for presentation,
and optional file attachments (images, archives, etc.)</li>
<li>to make it easy for other people to access this information through
a Web interface, browse entries, search, download files, and
optionally add, update, delete or comment on entries.</li>
</ol>
<p><strong>ELOG</strong> is a remarkable implementation of a <em>weblog</em> in at least two
respects :</p>
<ul>
<li>
<p>its simplicity of use : you don\'t need to be a seasoned server
operator and/or an experimented database administrator to run <strong>ELOG</strong>
; one executable file (under Unix or Windows), a simple configuration
text file, and it works. No Web server or relational database
required. It is also easy to translate the interface to the
appropriate language for your users.</p>
</li>
<li>
<p>its versatility : through its single configuration file, <strong>ELOG</strong> can
be made to display an infinity of variants of the <em>weblog</em> concept.
There are options for what to display, how to display it, what
commands are available and to whom, access control, etc. Moreover, a
single server can host several <em><em>weblog</em>s</em>, and each <em>weblog</em> can be
totally different from the rest.</p>
</li>
</ul>
<p>This is actually a problem when writing a User's Guide, because
<strong>ELOG</strong> servers, and individual <strong>weblogs</strong> on one server, can vary
wildly in appearance and functionality... This guide only attempts to
cover the main concepts of importance for <strong>ELOG</strong> users, describing
the default "<em>out-of-the-box</em>" setup and how that behaviour may have
been modified by the server administrator.</p>
<h2 id="what-words-mean-here">What Words Mean Here</h2>
<p>Just to be clear, some definitions of terms that will be used throughout
the guide :</p>
<ul>
<li><strong>ELOG server</strong> : the machine on which the <strong>ELOG</strong> server is run. Its
operating system (Windows/Unix/Linux) and status (server/desktop) are
not important, and of course it will probably do many other things
besides.</li>
<li><strong>ELOG administrator</strong> : the person who has the authority to modify
the <strong>ELOG</strong> configuration file on the server. May be an actual system
administrator, a normal user of a server, or just the owner of a
Windows PC.</li>
<li><strong>logbook</strong> : a <em>weblog</em> made available by the <strong>ELOG</strong> server. There
may be many distinct such logbooks on one server.</li>
<li><strong>entry</strong> : the individual piece of information in a logbook. Can be
as basic as a text message with a time-stamp, or carry much more
information : attributes (see below), HTML markup, links, attached
files...</li>
</ul>
<h2 id="accessing-an-elog-server-and-its-logbooks">Accessing an ELOG server and its logbook(s)</h2>
<p>To access a logbook, point your Web browser at the appropriate URL. The
default for a local Elog is <strong><code>http://localhost:8080/logbookname</code></strong>.
Logbook files are stored in directory <strong><code>logbookname</code></strong> which is a
sub-directory of the logbook root directory, defined by the
administrator. See the administrator guide on how to create a new
logbook.</p>
<p>If several logbooks are defined on the server, the entry page may be a
list of all logbooks, with their descriptions, number of entries, and
links to enter the logbook you want to use.</p>
<p>Alternatively, you may be taken directly to a specific logbook. By
default you will see a list of entries, but the administrator may have
defined a different "<em>default view</em>" for the logbook, like the list of
the day\'s entries, or directly display the last entry, etc. (depending
on what is most convenient for that logbook\'s purpose).</p>
<p>Each entry in a logbook is identified by an unique ID, which is last
part of the URL when that message is displayed. This ID might be used to
create a bookmark in a browser pointing directly to a specific entry.</p>
<p>There are four ways through which access to a logbook may be controlled:
it may be open for all to read ; it may require a common "<em>read</em>"
password for all users ; it may require each user to have an individual
user account (login name) and password ; finally, access may be granted
or not depending on the address of the workstation you are using.</p>
<h2 id="viewing-information-in-elog">Viewing information in ELOG</h2>
<p>There are two main viewing modes in a logbook :</p>
<ul>
<li>the "<strong>entry</strong>" view : this is when only one entry is displayed on
screen (like the latest entry when you first enter a logbook, or if
you click on one in a list). Here are the various parts of the display
:</li>
<li>
<p>if there are several logbooks on the <strong>ELOG</strong> server you will see a
row of "<em>tabs</em>" at the top with the names of all the logbooks.
These are link that allow to switch quickly between logbooks (<em>this
may be disabled</em>).</p>
</li>
<li>
<p>below is a title bar with the name of the current logbook at the
left, and the <strong>ELOG</strong> logo at the right. If you are logged in,
there will be a "<code>Logged in as &lt;username&gt;</code>" reminder in between.</p>
</li>
<li>
<p>next is the "<em>menu bar</em>" : on the left is a series of links or
buttons for <strong>ELOG</strong> commands available to you. These are explored
in the sections below (<em>Note: different users may see different
menus</em>). On the right is a "<em>VCR-like</em>" set of buttons for
browsing, also explained later (<em>this may be disabled</em>).</p>
</li>
<li>
<p>after these comes the actual entry information. It always starts
with the entry time-stamp, and may be followed by up to twenty
"<em>attributes</em>". These are like fields in a database and have been
defined specifically for the current logbook. Each attribute has a
checkbox besides it, explained below (<em>this may be disabled</em>).</p>
</li>
<li>
<p>the full-width box below holds the textual content (message) of the
entry. This can be plain-text or HTML code. Note that for some
special applications (say, a photo album or an event log) the
attributes and/or the attached files may be enough information, so
this field may not always be present.</p>
</li>
<li>
<p>last and optionally, one or more attached files (that were uploaded
to the server when the entry was created) are offered as clickable
links for download or viewing, along with the file name and size. If
these are images they may be displayed directly on the page.</p>
<p>At the bottom of every page is a common "<em>footer</em>" for the
logbook. By default this is just a link to the <strong>ELOG</strong> home page in
Switzerland, but may be customized locally (typically to provide a
navigation bar and links for integration with other Web sites).
- the "<strong>search result</strong>" views : these are basically lists of
entries, resulting either from a "<em>Search</em>" command or from
shortcuts such as "<em>Last X days</em>" and "<em>Last X entries</em>" commands
(more on this below). This mode has many options, including :
- a "<em>summary</em>" view : one entry per row in a table. Some attributes
may not be displayed. If the entry text is displayed (or its first
few lines), it goes into the rightmost column. Attachments are not
displayed.</p>
</li>
<li>
<p>a "<em>classical weblog</em>" view : entries appear beneath one another,
with attributes on one line and the text (and attachments, if
present) below. Images may be displayed or just linked to.</p>
</li>
<li>
<p>entries may appear most recent first, or in reverse.</p>
</li>
<li>
<p>menus on list views are different from the entry view menu. By
default they only have two or three commands, but they may have been
customized by the administrator to add more.</p>
<p>All these lists have a number to the left of each listed entry, that
is a link to the corresponding entry view.</p>
</li>
</ul>
<h2 id="browsing-around-and-finding-things">Browsing around and finding things</h2>
<p>There are several interesting ways to peruse the information in a
logbook :</p>
<ul>
<li><strong>weblogs</strong>" are often used for applications where chronology (time) is
relevant, so a very common approach is to see "<em>what happened
last</em>". In <strong>ELOG</strong> there are two commands for this. They are
actually shortcuts for searches, to display the last day\'s (24 hrs)
entries, or the last 10 entries (regardless of age). Note that the
menus on the "<em>search result</em>" views of these commands are a bit
special : they have the same command that created them, but with the
search "<em>interval</em>" doubled. From the "<em>last day</em>" list you can
get the "<em>last 2 days</em>" list, from that one the "<em>last 4 days</em>",
etc., and similarly for "<em>last 10</em>", "<em>last 20</em>", etc., making it
easy to quickly go back in time.</li>
<li>another useful method, very specific to <strong>ELOG</strong>, is "<em>filtered
browsing</em>" - again, shortcuts for specific searches. On the entry
view, the "<em>VCR</em>" buttons normally let you see the previous, next,
first or last entry in the logbook. However, if on the current entry
you check one (or more) of the checkboxes in front of the attributes,
only entries having the same value for the checked attribute(s) will
be displayed by the browse buttons. Thus you can quickly flip through
all the entries you submitted yourself, or of a certain type/category,
depending on what attributes have been defined.</li>
<li>for custom searches there is the query form given by the "<em>Find</em>"
command. This lets you look for entries between two dates, with
particular values for any attribute, or containing specific text. If
you fill in several fields, only entries that meet <strong>ALL</strong> criteria
will be selected. Possible options include sort order and summary view
for results, printer-friendly formatting, displaying attachments or
not, and searching through all logbooks on the <strong>ELOG</strong> server (if
applicable).</li>
</ul>
<h2 id="adding-stuff-to-a-logbook">Adding stuff to a logbook</h2>
<p>If you have "<em>write access</em>" to a logbook (by one of the same four
methods as for read access), then you may use the "<em>New</em>", "<em>Edit</em>",
"<em>Reply</em>" and "<em>Delete</em>" commands.</p>
<p>For the quality of the information committed to the logbook, you need
understand and use these as well as possible. Here are some of the
important features for each commmand :</p>
<ul>
<li><strong>New</strong> :</li>
<li>you will not be able to save your entry if all attributes marked
with a red star (*) are not filled in.</li>
<li>some attributes may be pre-filled from system variables (like your
user name). Pre-filled attributes may be still editable or read-only
(like the entry creation date).</li>
<li>attributes may be text fields (limited to 100 characters),
list-boxes (max. 100 values), or check-boxes. There is also a
special type of attribute where several values are listed on a line
with check-boxes, and you can check as many values as needed.</li>
<li>a nice touch : URLs in attributes (http://..., ftp://...,
mailto:...) are automatically converted to links.</li>
<li>in addition to the above URLs, one can enter a tag <strong>elog:\&lt;id&gt;</strong>
which references another logbook entry. The tag
<strong>elog:\&lt;logbook&gt;/\&lt;id&gt;</strong> references a message in another logbook
on the same server. The tag <strong>elog:\&lt;id&gt;/\&lt;n&gt;</strong> references
attachment number <strong>n</strong> in a logbook entry. To reference an
attachment in the current message, one uses <strong>elog:/\&lt;n&gt;</strong>. An
anchor inside an entry can be referenced with
<strong>elog:\&lt;id&gt;#\&lt;anchor&gt;</strong>.</li>
<li>the Text multi-line field, if present, may be pre-filled with a
template if entries need to have a common, consistent format across
the logbook (especially for HTML). There may also be a comment
inserted before it to explain local rules and conventions, upload
rules, etc.</li>
<li>check the "<em>Submit as HTML</em>" box if the entry contains HTML
markup.</li>
<li>a logbook may be configured to send a notification e-mail to various
recipients each time an entry is submitted. This may be the default
behaviour, and you should check "<em>Suppress notification</em>"" if it is
not wanted. Or it may be checked by default, and you need to
explicitely uncheck it to send the mail. Then again, you may not
have a choice... (note that notifiation recipients may or may not
be disclosed).</li>
<li>if the logbook allows attachments, there will be a number of fields
with "<em>Browse</em>" buttons at the bottom of the form. Use these to
pick one or more files on your local computer, they will be uploaded
to the <strong>ELOG</strong> server as you submit the form. IMPORTANT : there is
an upper limit on the size of individual attached files. By default
it is about 1 MB but can be changed by the administrator.</li>
<li><strong>Edit</strong> :</li>
<li>normally the Edit form will have all the values of the existing
entry in its fields for modification. However, sometimes you may see
fields that have been blanked if this makes sense for a particular
logbook application (e.g. a "<em>Last modified by</em>" field).</li>
<li>the "<em>Submit as new entry</em>" checkbox only appears on Edit forms.
If it is unchecked, the modified entry keeps its original creation
time-stamp. If it is checked, the modified entry becomes the latest
in the logbook, as if it had just been created. Again, it is
possible that this is checked by default, or disabled altogether on
some logbooks.</li>
<li>managing attachments through this form is easy. If all you want to
change is the attributes or text, don\'t touch the fields at the
bottom and the original attachments will be preserved. If you want
to add an additional attachment, use an empty field. If you want to
update an existing file, use the "<em>Browse</em>" button below that
file\'s name to specify the new one. Lastly, if you want to delete
an attachment without upoading a new one in its place, you must type
the magic word "<code>&lt;delete&gt;</code>" in the field below its name.</li>
<li><strong>Reply</strong> :</li>
<li>this command creates a new entry, but with the current entry\'s text
"<em>quoted</em>" (with \'&gt;\') in the compose form, much like when
replying to e-mail.</li>
<li>the new entry has a special "<em>In reply to</em>" attribute with a link
to the original entry ; the latter also acquires a "<em>Reply</em>"
attribute with a link to the new entry. Unfortunately these links
cannot be trusted in the present <strong>ELOG</strong> storage system, and the
whole scheme gets somewhat confusing when there are several replies.</li>
<li><strong>Delete</strong> :</li>
<li>nothing much to say about this one, except that there is no
"<em>Recycle bin</em>" or whatever : once you have confirmed the deletion
of an entry, it\'s gone for good, so be careful ! (same holds for
the replacement or deletion of an attached file).</li>
</ul>
<h2 id="misc-tips-tricks-things-to-be-aware-of">Misc. tips &amp; tricks, things to be aware of...</h2>
<ul>
<li>
<p>you can link directly to a specific entry by its URL, using the
message ID (from another entry or an external Web page). It is also
possible to link to a search result this way: use the "<em>Search</em>"
form to compose a query that will result in exactly what you want
(either a single entry or a list of entries). Copy the URL for that
result page from your browser, and use that as the target for your
link.</p>
</li>
<li>
<p>right now you cannot search entries for attachments by their file
name.</p>
</li>
<li>
<p>right now attributes that consist of just a checkbox ("<em>boolean</em>")
can only be searched by "<em>checked</em>" state in the "<em>Search</em>" form.
However, if you start from an entry where that attribute is unchecked,
you can use "<em>filtered browsing</em>" to flip through all other entries
where it is also unchecked.</p>
</li>
<li>
<p>as mentioned above, the "<em>Reply</em>" command only provides a basic
comment/chat facility - a full-blown discussion board is not
<strong>ELOG</strong>'s purpose. If a logbook has a very specific purpose and
format (picture gallery, event log, file library etc.) it might be a
good idea to disable that command there and move all
chat/comments/discussions to a separate, dedicated logbook to avoid
"<em>visual pollution</em>".</p>
</li>
<li>
<p>it is important to understand that currently the <strong>ELOG</strong> server
application is "<em>single-process</em>" and "<em>non-streaming</em>". In normal
terms this means that :</p>
</li>
<li>
<p>only one request is processed at any one time by the server.</p>
</li>
<li>
<p>uploading or downloading an attachement file is a single request,
and causes the entire file to be loaded in server memory while the
request is being processed.</p>
<p>This is not normally a problem for the sort of short, text-mode
entries <strong>ELOG</strong> is designed to support. However, if a user starts
to upload or download a large attachment file (or image) over a slow
link, all other users on that <strong>ELOG</strong> server will have to wait for
that transfert to finish before they can access any logbook on that
server. This is why there is a low limit on the size of attachments,
and why <strong>ELOG</strong> should not be used to distribute large files under
intensive multi-user conditions.</p>
</li>
<li>
<p>It is possible to use bookmarks to pre-populate various attributes
when submitting an <strong>ELOG</strong> entry. This can be useful if the same
person often creates similar entries from the same PC. For example,
with a bookmark of the form:</p>
<p>http://your.host/your_logbook/?cmd=New&amp;pauthor=joe&amp;ptype=Info</p>
</li>
</ul>
<p>...a new entry is created, with the "<em>author</em>" field pre-populated
with "<em>joe</em>" and the "<em>Info</em>" value preselected for the "<em>type</em>"
field. The same is possible for any attribute defined in the logbook
(note the leading "p"). Thus you can define a set of bookmarks for
various types of logbook entries.</p>
<h2 id="elog-command-line-client">elog command line client</h2>
<p>In addition to submission of logbook entries through the Web interface, the standalone "<em>client</em>" program <strong><code>elog</code></strong> can be used.</p>
<p>The parameters are:</p>
<pre><code class="language-text">elog &lt;parameters&gt;
-h &lt;hostname&gt; Hostname where elogd is running
[-p port] Port where elogd is running
[-d subdir] URL Directoy where elogd is running
-l logbook Name of logbook
-s Use SSL for communication
[-v] For verbose output
[-w password] Write password defined on server
[-u username password] User name and password
[-f &lt;attachment&gt;] Up to 50 attachments
-a &lt;attribute&gt;=&lt;value&gt; Up to 50 attributes
[-r &lt;id&gt;] Reply to existing message
[-q] Quote original text on reply
[-e &lt;id&gt;] Edit existing message
[-x] Suppress email notification
[-n 0|1|2] Encoding: 0:ELcode,1:plain,2:HTML
-m &lt;textfile&gt;] | &lt;text&gt;
</code></pre>
<p>Arguments with blanks must be enclosed in quotes. The elog message can
either be submitted on the command line, piped in like</p>
<p><code>cat text | elog -h ... -l ... -a ...</code></p>
<p>or in a file with the -m flag. Multiple attributes and attachments can
be supplied. If attributes with multiple possible values are defined
in a logbook (via the <em>"MOptions"</em> keyword), they can be separated
with a "|", like <strong><code>-a "&lt;attribute&gt;=&lt;value1&gt; | &lt;value2&gt;"</code></strong>. The
message text can be supplied directly at the command line or submitted
from a file with the <strong><code>-m</code></strong> flag.</p>
<p>The <strong><code>elog</code></strong> program makes it possible to submit logbook entries
automatically by the system or from scripts. In some shift logbooks
this feature is used to enter alarm messages automatically into the
logbook.</p>
<h2 id="rss-feed">RSS Feed</h2>
<p>RSS (RDF Site Summrary or Really Simple Syntication) is a web feed
format to publish frequently new or updated ELOG entries. This is a bit
like the email notifications present in ELOG, but the RSS system does
not go through an email reader, but through a dedicated RSS reader. This
helps to seperate ELOG updates form other email or spam. An RSS
"channel" can be subscribed to, so one gets notified whenever a new or
updated entry exists. One can either use a dedicated RSS reader or
aggregator, or use the RSS functionality of a web browser, such as
Firefox or Google Reader.</p>
<p>To obtain the RSS feed, one simply has to request the file
<strong><code>elog.rdf</code></strong> from a logbook. For the ELOG forum, one can enter the URL</p>
<p><a href="https://elog.psi.ch/elogs/Forum/elog.rdf"><code>https://elog.psi.ch/elogs/Forum/elog.rdf</code></a></p>
<p>The browser then offers the possiblity to subscribe to that logbook:</p>
<p><img alt="" src="../img/rss.png" /></p>
<p>In case of "Live Bookmarks" in Firefox, new logbook entries
automatically appear in the bookmark list:</p>
<p><img alt="" src="../img/live_bookmarks.png" /></p>
<p>Standalone RSS reader can also notify the user of new entries with
dialog boxes and sounds. For a list of availabel RSS aggregators, see
<a href="http://en.wikipedia.org/wiki/Comparison_of_feed_aggregators">here</a>.</p>
</div>
</div><footer>
<div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
<a href=".." class="btn btn-neutral float-left" title="Home"><span class="icon icon-circle-arrow-left"></span> Previous</a>
<a href="../adminguide/" class="btn btn-neutral float-right" title="Admin guide">Next <span class="icon icon-circle-arrow-right"></span></a>
</div>
<hr/>
<div role="contentinfo">
<!-- Copyright etc -->
</div>
Built with <a href="https://www.mkdocs.org/">MkDocs</a> using a <a href="https://github.com/readthedocs/sphinx_rtd_theme">theme</a> provided by <a href="https://readthedocs.org">Read the Docs</a>.
</footer>
</div>
</div>
</section>
</div>
<div class="rst-versions" role="note" aria-label="Versions">
<span class="rst-current-version" data-toggle="rst-current-version">
<span><a href=".." style="color: #fcfcfc">&laquo; Previous</a></span>
<span><a href="../adminguide/" style="color: #fcfcfc">Next &raquo;</a></span>
</span>
</div>
<script src="../js/jquery-3.6.0.min.js"></script>
<script>var base_url = "..";</script>
<script src="../js/theme_extra.js"></script>
<script src="../js/theme.js"></script>
<script src="../search/main.js"></script>
<script>
jQuery(function () {
SphinxRtdTheme.Navigation.enable(true);
});
</script>
</body>
</html>
Reference in New Issue View Git Blame Copy Permalink