From: Alexander Zeidler <a.zeidler@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 6/6] docs: replace path list with table for better readability
Date: Fri, 24 Nov 2023 18:43:47 +0100 [thread overview]
Message-ID: <20231124174347.200266-6-a.zeidler@proxmox.com> (raw)
In-Reply-To: <20231124174347.200266-1-a.zeidler@proxmox.com>
Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
---
docs/user-management.rst | 23 +++++++++++++----------
1 file changed, 13 insertions(+), 10 deletions(-)
diff --git a/docs/user-management.rst b/docs/user-management.rst
index 44040217..9c425eb4 100644
--- a/docs/user-management.rst
+++ b/docs/user-management.rst
@@ -329,16 +329,19 @@ references are specified in curly brackets.
Some examples are:
-* `/datastore`: Access to *all* datastores on a Proxmox Backup server
-* `/datastore/{store}`: Access to a specific datastore on a Proxmox Backup
- server
-* `/datastore/{store}/{ns}`: Access to a specific namespace on a specific
- datastore
-* `/remote`: Access to all remote entries
-* `/system/network`: Access to configure the host network
-* `/tape/`: Access to tape devices, pools and jobs
-* `/access/users`: User administration
-* `/access/openid/{id}`: Administrative access to a specific OpenID Connect realm
+.. table::
+ :align: left
+
+ =========================== =========================================================
+ ``/datastore`` Access to *all* datastores on a Proxmox Backup server
+ ``/datastore/{store}`` Access to a specific datastore on a Proxmox Backup server
+ ``/datastore/{store}/{ns}`` Access to a specific namespace on a specific datastore
+ ``/remote`` Access to all remote entries
+ ``/system/network`` Access to configure the host network
+ ``/tape/`` Access to tape devices, pools and jobs
+ ``/access/users`` User administration
+ ``/access/openid/{id}`` Administrative access to a specific OpenID Connect realm
+ =========================== =========================================================
Inheritance
^^^^^^^^^^^
--
2.39.2
next prev parent reply other threads:[~2023-11-24 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 17:43 [pbs-devel] [PATCH proxmox-backup 1/6] docs: add "Wiki" to sidebar Alexander Zeidler
2023-11-24 17:43 ` [pbs-devel] [PATCH proxmox-backup 2/6] docs: improve the occurrence of product website hyperlinks Alexander Zeidler
2023-11-24 17:43 ` [pbs-devel] [PATCH proxmox-backup 3/6] docs: epilog: update hyperlinks Alexander Zeidler
2023-11-24 17:43 ` [pbs-devel] [PATCH proxmox-backup 4/6] docs: pbs2to3: fix and improve wording Alexander Zeidler
2023-11-24 17:43 ` [pbs-devel] [PATCH proxmox-backup 5/6] docs: fix typos Alexander Zeidler
2023-11-24 17:43 ` Alexander Zeidler [this message]
2023-11-25 15:23 ` [pbs-devel] applied: [PATCH proxmox-backup 1/6] docs: add "Wiki" to sidebar Thomas Lamprecht
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=20231124174347.200266-6-a.zeidler@proxmox.com \
--to=a.zeidler@proxmox.com \
--cc=pbs-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