From: Lunar <email@example.com> To: Eric Wong <firstname.lastname@example.org> Cc: Hleb Valoshka <email@example.com>, firstname.lastname@example.org, email@example.com Subject: Re: TAN: Coquelicot Date: Wed, 1 Jul 2015 13:54:31 +0200 [thread overview] Message-ID: <20150701115431.GC26527@loar> (raw) In-Reply-To: <20150630231915.GA15360@dcvr.yhbt.net> [-- Attachment #1: Type: text/plain, Size: 1098 bytes --] Eric Wong: > Lunar <firstname.lastname@example.org> wrote: > > Rainbows! is used by Coquelicot: > > https://coquelicot.potager.org/ > > > > The project needs some love, but I know about several installations that > > are used on a daily basis. > > Interesting! I'm honestly a bit disappointed it's not a generic Rack > app and depends on certain server features, but the project seems mostly > inline with my interests. In the very first versions, it was a generic Rack app. And then I discovered that the file that was transmitted was saved in clear before being given to the handler (where it would get encrypted)… Finding that Rainbows! could be made to process the incoming bytes directly really helped in fixing this issue. The choice of tying it to a single HTTP server is also a conscious decision to make it easy to install. On Debian, it only requires `apt-get install coquelicot` and then 3 lines in Apache configuration. > But if I were to run it, I'd remove all CSS+images+JS and might > contribute a patch to disable that all, too :) Why not. :) -- Lunar
prev parent reply other threads:[~2015-07-01 11:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20150615225652.GA16164@dcvr.yhbt.net> [not found] ` <CAAB-Kckrnj0dJY02AeRsN87eBDg-BYXhNnkPU+fvxLcAh2ta7g@mail.gmail.com> 2015-06-23 20:04 ` [ANN] unicorn 5.0.0.pre1 - incompatible changes! Eric Wong 2015-06-23 20:42 ` Damian Janowski 2015-06-24 9:19 ` Lunar 2015-06-30 23:19 ` TAN: Coquelicot Eric Wong 2015-07-01 11:54 ` Lunar [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://yhbt.net/rainbows/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20150701115431.GC26527@loar \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: TAN: Coquelicot' \ /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
Code repositories for project(s) associated with this inbox: ../../rainbows.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).