README.adoc

   1 Proxmox VE Documentation
   2 ========================
   3 include::attributes.txt[]
   4
   5 We try to generate high quality documentation for
   6 http://www.proxmox.com[Proxmox VE], and choose to use
   7 http://www.methods.co.nz/asciidoc/[AsciiDoc] as base format.
   8
   9 The basic idea is to generate high quality manual pages, and assemble
  10 them into a complete book, called link:pve-admin-guide.adoc[Proxmox VE
  11 Administration Guide].  So we have one source, and generate several
  12 documents from that. It is also possible to generate printable PDF
  13 files, or ebook formats ('.ebup').
  14
  15 When possible, we provide scripts to extract API definitions,
  16 configuration or command line options from the source code.
  17
  18 To simplify the documentation task, we keep all Documentation within
  19 this repository. It is possible to generate the docs (without installing
  20 any additional Proxmox packages) with:
  21
  22  make index
  23
  24
  25 Debian Packages
  26 ---------------
  27
  28 We generate a development package called 'pve-doc-generator', which is
  29 used by other Proxmox VE package to generate manual pages at package
  30 build time.
  31
  32 Another package called 'pve-docs' is used to publish generated
  33 '.html' and '.pdf' files on our web servers. You can generate
  34 those debian packages using:
  35
  36  make deb
  37
  38
  39 Common Macro definition in link:attributes.txt[]
  40 ------------------------------------------------
  41
  42 'asciidoc' allows us to define common macros, which can then be
  43 referred to using `{macro}`. We try to use this mechanism to improve
  44 consistency. For example, we defined a macro called `pve`, which
  45 expands to "Proxmox VE". The plan is to add more such definitions for
  46 terms which are used more than once.
  47
  48 Autogenerated CLI Command Synopsis
  49 ----------------------------------
  50
  51 We generate the command line synopsis for all manual pages
  52 automatically. We can do that, because we have a full declarative
  53 definition of the {pve} API. I added those generated files
  54 ('*-synopsis.adoc') to the git repository, so that it is possible to
  55 build the documentation without having a fully installed {pve}
  56 development environment.
  57
  58 Copyright
  59 ---------
  60
  61 Copyright (C) 2016 Proxmox Server Solutions Gmbh
  62
  63 Permission is granted to copy, distribute and/or modify this document
  64 under the terms of the GNU Free Documentation License, Version 1.3 or
  65 any later version published by the Free Software Foundation; with no
  66 Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
  67 copy of the license is included in the link:LICENSE[LICENSE] file.