Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Jeroen van Veen <>
To: Juliusz Chroboczek <>
Cc: "" <>
Subject: [Galene] Re: Docker config?
Date: Thu, 24 Dec 2020 14:25:19 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Op woensdag, december 23, 2020 2:33 PM, Juliusz Chroboczek <> schreef:

> 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 page. Please let me know when
> it's tested and you believe it's ready for public consumption.

I'm not really sure about the current Docker build yet. It may be a problem to
keep in sync with development, unless its generated from a ci. I'll try some
things first and let you know when I have something workable.

> > -   Move most documentation from the README to a Github 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
> (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
> > 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.

Great! I made a small PR ( Please let
me know if it needs more work. I'm still quite unfamiliar with Golang.

> -- Juliusz
> Galene mailing list --
> To unsubscribe send an email to

      parent reply	other threads:[~2020-12-24 14:25 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 ` [Galene] " Juliusz Chroboczek
2020-12-23 13:49   ` 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 [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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \
    --subject='[Galene] Re: Docker config?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox