From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Noel Ullreich <n.ullreich@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-docs 2/3] Fixed the table in 3.11.8
Date: Tue, 3 Jan 2023 16:35:09 +0100 [thread overview]
Message-ID: <0bfa9e88-4f57-e4d4-2087-caf572a85aaa@proxmox.com> (raw)
In-Reply-To: <20230103133121.114234-3-n.ullreich@proxmox.com>
Am 03/01/2023 um 14:31 schrieb Noel Ullreich:
> Fixed the table by manually replacing the characters latex could not
> render with simpler characters. This will have to be done manually
> again for any future tables of the same style for now.
you don't remove the old one though...?
>
> Signed-off-by: Noel Ullreich <n.ullreich@proxmox.com>
> ---
> certificate-management.adoc | 24 ++++++++++++++++++++++--
> 1 file changed, 22 insertions(+), 2 deletions(-)
>
> diff --git a/certificate-management.adoc b/certificate-management.adoc
> index edf0468..f481916 100644
> --- a/certificate-management.adoc
> +++ b/certificate-management.adoc
> @@ -292,10 +292,29 @@ root@proxmox:~# echo "OVH_CK=ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ" >> /path/to/api-t
> ----
>
> Now you can setup the the ACME plugin:
> -
> ----
> root@proxmox:~# pvenode acme plugin add dns example_plugin --api ovh --data /path/to/api_token
> root@proxmox:~# pvenode acme plugin config example_plugin
> + ---------------------------------------------------
> +| key | value |
> + ---------------------------------------------------
> +| api | ovh |
> + ---------------------------------------------------
> +| data | OVH_AK=XXXXXXXXXXXXXXXX |
> +| | OVH_AS=YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY |
> +| | OVH_CK=ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ |
> + ---------------------------------------------------
> +| digest | 867fcf556363ca1bea866863093fcab83edf47a1 |
> + ---------------------------------------------------
> +| plugin | example_plugin |
> + ---------------------------------------------------
> +| type | dns |
> + ---------------------------------------------------
> +----
> +
> +////
> +actually looks like this but this won't render, not even in xetex
> +with --fop, a2x can kinda handle it but that breaks other stuff
> ┌────────┬──────────────────────────────────────────┐
> │ key │ value │
> ╞════════╪══════════════════════════════════════════╡
> @@ -311,7 +330,8 @@ root@proxmox:~# pvenode acme plugin config example_plugin
> ├────────┼──────────────────────────────────────────┤
> │ type │ dns │
> └────────┴──────────────────────────────────────────┘
> -----
> +////
> +
>
> At last you can configure the domain you want to get certificates for and
> place the certificate order for it:
next prev parent reply other threads:[~2023-01-03 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 13:31 [pve-devel] [PATCH pve-docs 0/3] Fixed formatting of pdf docs Noel Ullreich
2023-01-03 13:31 ` [pve-devel] [PATCH pve-docs 1/3] Fixed inline code breaking in " Noel Ullreich
2023-01-03 15:36 ` Thomas Lamprecht
2023-01-03 13:31 ` [pve-devel] [PATCH pve-docs 2/3] Fixed the table in 3.11.8 Noel Ullreich
2023-01-03 15:35 ` Thomas Lamprecht [this message]
2023-01-10 12:56 ` Noel Ullreich
2023-01-03 13:31 ` [pve-devel] [PATCH pve-docs 3/3] Fixed kerning in table of contents Noel Ullreich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0bfa9e88-4f57-e4d4-2087-caf572a85aaa@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=n.ullreich@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox