From: Jeroen van Veen <jvanveen@protonmail.com> To: "galene@lists.galene.org" <galene@lists.galene.org> Subject: [Galene] Docker config? Date: Wed, 23 Dec 2020 03:18:06 +0000 [thread overview] Message-ID: <0bovnrx2Yq176RacwUPyC-0d5CP90GDlmJ-X1A91KkSxoD6RsctVvD7l6PJ8bJTjvjWWxFs30MZ0pvqPbQ96TIxWIP9kpxFDTFTgQ2H4kLU=@protonmail.com> (raw) [-- Attachment #1: Type: text/plain, Size: 1696 bytes --] Hello, Thank you for open-sourcing Galene. I already love it! Its a breeze to get it up and running. I'm currently evaluating it on a VPS behind a NGINX proxy (https://galene.ca11.app/). From a fork (https://github.com/garage44/galene/) I'm trying out some ideas. Hope these bulletpoints don't offend anyone; I'm just excited about the software and looking for ways to contribute. Probably not useful for the project at all, but maybe some things might stick: * Create small docker image for one-line "try-out" setup (not tested from other machines) Most people seem to love short readme texts with just a few setup steps. Maybe a minimal docker image is a good way to have an even faster "try-out" experience for interested people? * Move most documentation from the README to a Github wiki (https://github.com/garage44/galene/wiki) A lot of documentation in the README! How about moving it a level further away from the README, so the README only contains a project description and the bare minimum of setup/developer instructions? This would also make it easier for users to contribute documentation, without intervering with the code-base. * 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. The Github readme seems to be the landing page for most people new to an open-source project. Maybe that would make it worth considering to rename it after all? * 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. Cheers, Jeroen [-- Attachment #2: Type: text/html, Size: 2565 bytes --]
next reply other threads:[~2020-12-23 3:18 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-23 3:18 Jeroen van Veen [this message] 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
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='0bovnrx2Yq176RacwUPyC-0d5CP90GDlmJ-X1A91KkSxoD6RsctVvD7l6PJ8bJTjvjWWxFs30MZ0pvqPbQ96TIxWIP9kpxFDTFTgQ2H4kLU=@protonmail.com' \ --to=jvanveen@protonmail.com \ --cc=galene@lists.galene.org \ --subject='Re: [Galene] Docker config?' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox