From: Juliusz Chroboczek <jch@irif.fr>
To: "printpagestopdf@yahoo.de" <printpagestopdf@yahoo.de>
Cc: "galene@lists.galene.org" <galene@lists.galene.org>
Subject: [Galene] Re: Additional infos about the WP Plugin
Date: Tue, 11 Apr 2023 22:34:20 +0200 [thread overview]
Message-ID: <87bkjuw437.wl-jch@irif.fr> (raw)
In-Reply-To: <790622636.3178670.1681242525967@mail.yahoo.com>
>> I'm wondering what I could do on the Galene side to simplify your
>> usage. In particular, would it be useful if you could just do an HTTPS
>> PUT (properly authentified) in order to update a group definition in
>> order to avoid sftp?
> Because for some of the "administrators" it is a barrier to set up sftp
> access or filesharing. So if such an easier alternative way would be
> available to manage the server groups would enhance the usability of the
> plugin.
It's also not atomic. With HTTP, we could use ETags to avoid the
lost-update problem. Definitely something to look into.
> P.S.: As I read Version 0.7.0 of Galene will have exactly one of the ideas the
> plugin does (invitation links) as a native implementation - very nice.
Hehe. You released your code just as I was working on native tokens, so
that's why I was asking how you implement them.
-- Juliusz
prev parent reply other threads:[~2023-04-11 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1533526394.8685685.1680708673432.ref@mail.yahoo.com>
2023-04-05 15:31 ` [Galene] " printpagestopdf
2023-04-10 14:10 ` [Galene] " Juliusz Chroboczek
2023-04-11 19:48 ` printpagestopdf
2023-04-11 20:34 ` Juliusz Chroboczek [this message]
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
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkjuw437.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=galene@lists.galene.org \
--cc=printpagestopdf@yahoo.de \
/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