From: Leo Nunner <l.nunner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v2 docs] config: remove reference to preceeding / from content-dirs
Date: Tue, 14 Mar 2023 14:14:56 +0100 [thread overview]
Message-ID: <20230314131456.165418-4-l.nunner@proxmox.com> (raw)
In-Reply-To: <20230314131456.165418-1-l.nunner@proxmox.com>
Signed-off-by: Leo Nunner <l.nunner@proxmox.com>
---
pve-storage-dir.adoc | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/pve-storage-dir.adoc b/pve-storage-dir.adoc
index 4eb8dcd..3367394 100644
--- a/pve-storage-dir.adoc
+++ b/pve-storage-dir.adoc
@@ -57,8 +57,7 @@ in the following format:
vtype=path
Where `vtype` is one of the allowed content types for the storage, and
-`path` is a path relative to the mountpoint of the storage, preceded
-with /.
+`path` is a path relative to the mountpoint of the storage.
.Configuration Example (`/etc/pve/storage.cfg`)
----
@@ -67,7 +66,7 @@ dir: backup
content backup
prune-backups keep-last=7
max-protected-backups 3
- content-dirs backup=/custom/backup/dir
+ content-dirs backup=custom/backup/dir
----
The above configuration defines a storage pool called `backup`. That pool can be
--
2.30.2
next prev parent reply other threads:[~2023-03-14 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 13:14 [pve-devel] [PATCH v2 storage manager docs] Expose content-dirs through GUI + use relative paths Leo Nunner
2023-03-14 13:14 ` [pve-devel] [PATCH v2 storage] config: use relative paths for content overrides Leo Nunner
2023-03-20 14:26 ` [pve-devel] applied: " Thomas Lamprecht
2023-03-14 13:14 ` [pve-devel] [PATCH v2 manager] gui: expose content-dirs property in storage edit/create Leo Nunner
2023-03-20 19:25 ` Thomas Lamprecht
2023-03-14 13:14 ` Leo Nunner [this message]
2023-03-20 19:10 ` [pve-devel] applied: [PATCH v2 docs] config: remove reference to preceeding / from content-dirs 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=20230314131456.165418-4-l.nunner@proxmox.com \
--to=l.nunner@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