From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Christian Ebner <c.ebner@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] applied: [PATCH proxmox-backup 0/6] fix various s3 related ui/cli/doc issues
Date: Wed, 23 Jul 2025 09:55:08 +0200 [thread overview]
Message-ID: <0c65ec0c-038d-4ac9-921a-1337eaf135b8@proxmox.com> (raw)
In-Reply-To: <706ed900-c034-4e99-8ea2-543dad670151@proxmox.com>
Am 23.07.25 um 09:37 schrieb Christian Ebner:
> On 7/23/25 9:27 AM, Thomas Lamprecht wrote:
>> Am 23.07.25 um 08:33 schrieb Christian Ebner:
>>> I see the first patch (tabs for remotes) was not applied, the Remotes and S3 Endpoints still separate in the side menu.
>>>
>>> Was this intentional?
>>
>> Yes, as indicated in a later commit, albeit naturally a bit subtle
>> in general:
>>
>> https://git.proxmox.com/?p=proxmox-backup.git;a=commit;h=3bbc9dedb9ed32e7c1af3bbcc4a6b1d02d852fc5
>
> Right, thanks for clarification!
Yeah, would have been better to reply on the patch directly, but it was late
and I figured you are not against doing this, being closer to your original
UI again after all.
background: While I still don't think that having in in remotes would be
wrong, PBS really is not as crowded as PVE, and I could well imagine that
for a significant user group S3 might become a prime feature, so having
it's dedicated tab is OK.
btw. nothing for the next weeks, but in the mid-term it might be nice to
get a simple dashboard or status here. We could add counters for sent and
received traffic from the endpoint grouped per bucket (or datastore),
information that would be naturally also interesting in the per-datastore
overview, but as said, nothing to worry much about for now, just mentioning
it as further argument for having S3 in its own top-level tab.
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-07-23 7:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 12:48 [pbs-devel] " Christian Ebner
2025-07-22 12:48 ` [pbs-devel] [PATCH proxmox-backup 1/6] ui: add tabs for remotes and move s3 endpoint config to it Christian Ebner
2025-07-22 12:48 ` [pbs-devel] [PATCH proxmox-backup 2/6] ui: use S3 endpoint over S3 client for ui elements Christian Ebner
2025-07-22 12:48 ` [pbs-devel] [PATCH proxmox-backup 3/6] cli: use `endpoint` over `client` for s3 endpoint subcommands Christian Ebner
2025-07-22 12:48 ` [pbs-devel] [PATCH proxmox-backup 4/6] docs: use `endpoint` over `client` for the s3 endpoint configuration Christian Ebner
2025-07-22 12:48 ` [pbs-devel] [PATCH proxmox-backup 5/6] ui: default for s3 overwrite-in-use to be disabled Christian Ebner
2025-07-22 12:48 ` [pbs-devel] [PATCH proxmox-backup 6/6] ui: s3 client edit: allow for https scheme prefix in endpoint input Christian Ebner
2025-07-22 20:25 ` [pbs-devel] applied: [PATCH proxmox-backup 0/6] fix various s3 related ui/cli/doc issues Thomas Lamprecht
2025-07-23 6:33 ` Christian Ebner
2025-07-23 7:27 ` Thomas Lamprecht
2025-07-23 7:37 ` Christian Ebner
2025-07-23 7:55 ` Thomas Lamprecht [this message]
2025-07-23 10:04 ` Christian Ebner
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=0c65ec0c-038d-4ac9-921a-1337eaf135b8@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.ebner@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