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 | ||
| 0e9c6c13 | 9 | pvenode - Proxmox VE Node Management |
| a99bdc62 FG |
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 | ||
| 0e9c6c13 | 26 | The {PVE} node management tool (`pvenode`) allows to control node specific |
| 9cbe129f TL |
27 | settings and resources. |
| 28 | ||
| aeecd9ea SI |
29 | Currently `pvenode` allows to set a node's description and to manage |
| 30 | the node's SSL certificates used for the API and the web GUI through `pveproxy`. | |
| 31 | ||
| 32 | EXAMPLES | |
| 33 | -------- | |
| 34 | `pvenode cert set certificate.crt certificate.key -force` | |
| 35 | ||
| 36 | Install an externally provided certificate. Both files need to be PEM encoded. | |
| 37 | `certificate.key` contains the private key and `certificate.crt` contains the | |
| 38 | whole certificate chain. | |
| 39 | ||
| 40 | ----- | |
| 41 | pvenode acme account register default mail@example.invalid | |
| 42 | pvenode config set --acme domains=example.invalid | |
| 43 | pvenode acme cert order | |
| 44 | systemctl restart pveproxy | |
| 45 | ----- | |
| 46 | ||
| 0e9c6c13 | 47 | Setup ACME account and order a certificate for local node. |
| 9cbe129f TL |
48 | |
| 49 | // TODO: extend and improve chapter! | |
| a99bdc62 FG |
50 | |
| 51 | ifdef::manvolnum[] | |
| 52 | include::pve-copyright.adoc[] | |
| 53 | endif::manvolnum[] |