[Galene] Re: Docker config?

[Jeroen van Veen <jvanveen@protonmail.com>]

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Op woensdag, december 23, 2020 2:33 PM, Juliusz Chroboczek <jch@irif.fr> 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 galene.org 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
> >     (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.


Great! I made a small PR (https://github.com/jech/galene/pull/16). Please let
me know if it needs more work. I'm still quite unfamiliar with Golang.


>
> -- Juliusz
>
> Galene mailing list -- galene@lists.galene.org
> To unsubscribe send an email to galene-leave@lists.galene.org