From: Juliusz Chroboczek <jch@irif.fr>
To: Jeroen van Veen <jvanveen@protonmail.com>
Cc: "galene@lists.galene.org" <galene@lists.galene.org>
Subject: [Galene] Re: Docker config?
Date: Wed, 23 Dec 2020 14:33:48 +0100 [thread overview]
Message-ID: <87y2ho1war.wl-jch@irif.fr> (raw)
In-Reply-To: <0bovnrx2Yq176RacwUPyC-0d5CP90GDlmJ-X1A91KkSxoD6RsctVvD7l6PJ8bJTjvjWWxFs30MZ0pvqPbQ96TIxWIP9kpxFDTFTgQ2H4kLU=@protonmail.com>
Thanks for the kind words, Jeroen.
> * Create small docker image for one-line "try-out" setup
That's cool. I'm not going to include it in Galene, since I don't run
Docker myself and would be unable to maintain your contribution, but I'll
be glad to put a link to the galene.org page. Please let me know when
it's tested and you believe it's ready for public consumption.
> * Move most documentation from the README to a Github wiki
> (https://github.com/garage44/galene/wiki)
I'm trying to avoid relying too much on third parties, and to keep as much
as possible within Git. A git repository is easy to migrate if we decide
to change providers, not so with a Github wifi. If people think that
a Wiki is necessary, we could conceivably put one on galene.org.
(Toke, who's kindly administering this mailing list, is publishing the
list archives as a Git repository, so that we can migrate away at any
point. I see no reason to migrate away from Toke, but I wouldn't want to
use a mailing list provider who doesn't make that possible.)
(Now if somebody were to design a usable issue tracker that allows easy
migration, my happiness would be complete.)
> * Rename README to README.md
> It's annoying that Github doesn't parse a README as markdown by default,
> but it improves the readability on the Github frontpage a lot.
Yep. I've reported the issue to the Github people, they told me to f*ck off.
Another reason to avoid relying too much on Github.
> * Option to disable TLS
> Would it be an idea to let Nginx sort this out? Most people are already
> familiar with a Letsencrypt/Certbot/Nginx
> setup. Galene could have less config in that case to worry about.
Yes, that makes sense. The reason Galène doesn't support HTTP is that
WebRTC requires a secure context. I'd be glad to accept a pull request to
conditionally disable HTTPS.
-- Juliusz
next prev parent reply other threads:[~2020-12-23 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 3:18 [Galene] " Jeroen van Veen
2020-12-23 13:33 ` Juliusz Chroboczek [this message]
2020-12-23 13:49 ` [Galene] " Antonin Décimo
2020-12-23 14:47 ` Juliusz Chroboczek
2020-12-23 15:14 ` Antonin Décimo
2020-12-24 14:25 ` Jeroen van Veen
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=87y2ho1war.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=galene@lists.galene.org \
--cc=jvanveen@protonmail.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