projects / pve-docs.git / blame
| Commit | Line | Data |
|---|---|---|
| a99bdc62 FG |
1 | ifdef::manvolnum[] |
| 2 | pvenode(1) | |
| 3 | ========== | |
| 4 | :pve-toplevel: | |
| 5 | ||
| 6 | NAME | |
| 7 | ---- | |
| 8 | ||
| 9 | pvenode - Proxmox VE Node Management | |
| 10 | ||
| 11 | SYNOPSIS | |
| 12 | -------- | |
| 13 | ||
| 14 | include::pvenode.1-synopsis.adoc[] | |
| 15 | ||
| 16 | DESCRIPTION | |
| 17 | ----------- | |
| 18 | endif::manvolnum[] | |
| 19 | ||
| 20 | ifndef::manvolnum[] | |
| 21 | Proxmox Node Management | |
| 22 | ======================= | |
| 23 | :pve-toplevel: | |
| 24 | endif::manvolnum[] | |
| 25 | ||
| 9cbe129f TL |
26 | The {PVE} node management tools (`pvenode`) allows to control node specific |
| 27 | settings and resources. | |
| 28 | ||
| 29 | Currently the `pvenode` tool allows to manage the node's SSL certificates used | |
| 30 | for API and the web GUI. It includes an implementation of the **A**utomatic | |
| 31 | **C**ertificate **M**anagement **E**nvironment (ACME) protocol, allowing {pve} | |
| 32 | admins to interface with Let's Encrypt, with which trusted certificates can be | |
| 33 | generated and setup easily. | |
| 34 | ||
| 35 | // TODO: extend and improve chapter! | |
| a99bdc62 FG |
36 | |
| 37 | ifdef::manvolnum[] | |
| 38 | include::pve-copyright.adoc[] | |
| 39 | endif::manvolnum[] |