Self-hostability

[Evernight]

If you're interested in exploring proper self-hostability (more reliable server not requiring restarts, secured setup, authentication, etc), vote for this issue.

[acciptris]

I was able to successfully self-host lazy-beancount using Authelia. However, since I was not sure about the security of the setup, I did not use it further. I can share my configuration files here after cleaning them.

[Evernight]

@acciptris thanks for sharing! Yeah, that's why I have a note in the README currently. What this project is is kinda evolving over time but initially using Docker was just a way to solidify requirements and make sure there's an easy and reproducible way to run these packages on a variety of systems (that are supposed to be mostly laptops or personal PC for now). Self-hosting this feels like a natural thing to do but without feeling like I have enough expertise to give good recommendations I opted to adding that disclaimer instead.

I don't think launching it and keeping up on a server is hard per se but the primary issues are:

1. There are some operations and cases that still require server restarts.
   It's not optimal but doesn't cause many problems for me personally. Would be good to fix and probably not too much work but I haven't prioritized this especially as some of the UIs and approaches are still prototype-y and I'd like to evolve them more before focusing on stability.

2. And yeah, security of course. One of the features of this setup that I think are very important is an ability to keep all of the data private. But these tools are very flexible, with plugin system based on arbitrary Python code and such, and I suppose it opens a big surface of attack if not treated very carefully. Yeah, I was imagining using a dedicated tool (thanks for mentioning Authelia, looks very similar to what would be needed) for handling authorization as opposed to adding this to fava or other frontends. But then making sure that best practices are used and nothing is left exposed to the outer web other than the minimal stuff that should be.

Basically, similar to what has been mentioned here: beancount/fava#314. Also https://github.com/zsxsoft/fava-management mentioned there but I'd personally prefer strict firewalls and reverse proxies (maybe they are not mutually exclusive with that project though).