On Sun, Dec 30, 2018 at 01:24:23AM +0100, Pierre-Elliott Bécue wrote: > I think a webserver config + WSGI handling is quite overkill. Do you agree?
Yeah, I agree. Upstream is reluctant to even document easy setup recipes on the basis that Fava is essentially a personal service. I've myself setup a "public" Fava, behind HTTPS auth of course, but I see value in not making it "too easy" in this case, for fear of unsavvy users leaking personal information out of the box. If anything, we should work with upstream on the deployment documentation side, and make sure said documentation is shipped with the package. Cheers PS I commented on IRC about that, but FWIW: I think the reference on the package description to "beancount" as package name is correct, because there is such a binary package and it is the end-user oriented entry point to Beancount in Debian -- Stefano Zacchiroli . z...@upsilon.cc . upsilon.cc/zack . . o . . . o . o Computer Science Professor . CTO Software Heritage . . . . . o . . . o o Former Debian Project Leader & OSI Board Director . . . o o o . . . o . « the first rule of tautology club is the first rule of tautology club »
signature.asc
Description: PGP signature
