From: Dylan Whyte <d.whyte@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH docs 0/7] Update for new content and sections
Date: Fri, 6 Nov 2020 15:46:23 +0100 [thread overview]
Message-ID: <20201106144630.21538-1-d.whyte@proxmox.com> (raw)
- Update certain instructions on how to find and do things
- Add screenshots for updated interface
- Add sections for Verification and Pruning
- Add a section descriping the change-owner command
- Add brief descriptions of the new datastore layout
- Remove references to things that no longer exist
- Fix minor formatting issues
Dylan Whyte (7):
installation & gui: Formatting fixup
backup-client: add section on change-owner command
datastore: description of new datastore view
Update where to find certain items since GUI update
maintenance: add verification and prune to section
Remove reference to backup@pam & old console msg
Add screenshots
docs/backup-client.rst | 30 +++++++--
docs/gui.rst | 35 ++++++-----
.../pbs-gui-administration-serverstatus.png | Bin 129701 -> 143238 bytes
.../screenshots/pbs-gui-apitoken-overview.png | Bin 0 -> 61312 bytes
.../pbs-gui-apitoken-secret-value.png | Bin 0 -> 18733 bytes
.../screenshots/pbs-gui-datastore-content.png | Bin 0 -> 92709 bytes
.../screenshots/pbs-gui-datastore-prunegc.png | Bin 0 -> 68080 bytes
.../screenshots/pbs-gui-datastore-summary.png | Bin 0 -> 133375 bytes
.../pbs-gui-datastore-verifyjob-add.png | Bin 0 -> 15455 bytes
.../pbs-gui-user-management-add-user.png | Bin 18938 -> 19871 bytes
.../screenshots/pbs-gui-user-management.png | Bin 55744 -> 63707 bytes
docs/installation.rst | 22 +++----
docs/maintenance.rst | 59 ++++++++++++++++--
docs/managing-remotes.rst | 16 ++---
docs/storage.rst | 11 ++--
docs/user-management.rst | 21 +++++--
16 files changed, 136 insertions(+), 58 deletions(-)
create mode 100644 docs/images/screenshots/pbs-gui-apitoken-overview.png
create mode 100644 docs/images/screenshots/pbs-gui-apitoken-secret-value.png
create mode 100644 docs/images/screenshots/pbs-gui-datastore-content.png
create mode 100644 docs/images/screenshots/pbs-gui-datastore-prunegc.png
create mode 100644 docs/images/screenshots/pbs-gui-datastore-summary.png
create mode 100644 docs/images/screenshots/pbs-gui-datastore-verifyjob-add.png
--
2.20.1
next reply other threads:[~2020-11-06 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 14:46 Dylan Whyte [this message]
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 1/7] installation & gui: Formatting fixup Dylan Whyte
2020-11-06 15:51 ` Dietmar Maurer
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 2/7] backup-client: add section on change-owner command Dylan Whyte
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 3/7] datastore: description of new datastore view Dylan Whyte
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 4/7] Update where to find certain items since GUI update Dylan Whyte
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 5/7] maintenance: add verification and prune to section Dylan Whyte
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 6/7] Remove reference to backup@pam & old console msg Dylan Whyte
2020-11-06 15:34 ` Dietmar Maurer
2020-11-09 7:38 ` Dylan Whyte
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 7/7] Add screenshots Dylan Whyte
2020-11-06 15:33 ` [pbs-devel] applied: [PATCH docs 0/7] Update for new content and sections Dietmar Maurer
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=20201106144630.21538-1-d.whyte@proxmox.com \
--to=d.whyte@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