forked from oVirt/ovirt-engine
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME.manual
57 lines (39 loc) · 1.65 KB
/
README.manual
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
ovirt-engine Manual
===================
OVERVIEW
--------
ovirt-engine supports a manual package for context sensitive help within the
application. Manual package is not provided by base package and should be
added externally.
PREPARATIONS
------------
Provided the manual package name is DOC_PACKAGE the following steps should
be followed.
1. Prepare manual which are static html files.
2. Create manual configuration file at manual.properties within root of
manual and create lookup index files to map between help tag and URI,
see format below.
3. Package manual pages at DOC_PACKAGE to be installed into filesystem, for
example:
/usr/share/doc/DOC_PACKAGE/manual
4. Tell engine where manual is, for example,
/etc/ovirt-engine/engine.conf.d/20-DOC_PACKAGE.conf
ENGINE_MANUAL="/usr/share/doc/DOC_PACKAGE/manual"
MANUAL CONFIGURATION FILE
-------------------------
ovirt-engine will read the manual.properties located at the root of
the manual content.
The format of this file is:
helptags.APPLICATION = [index1.json[, index2.json[, ....]]]
APPLICATION is the name of the application that issues the request
(e.g. webadmin or userportal), the value is list of json files relative to
configuration file that map between help tag and URI. Their content is
merged left to right, last wins.
The format of index mapping file is a JSON object. Key is help tag and value
is uri relative to the package, for example:
{
"create_new_vm": "newvm.html",
"delete_vm": "delvm.html",
}
The index file can be generated out of source code or compared to source
code using build/helptag.py tool available within engine source repository.