Misc. fixes from first use

Hi,

Thanks for creating this it's pretty cool! Here's a couple fixes I did when getting it to work for me. I have a bit of an unusual setup: I use NixOS and manage my config in Nix files, which then generate the config for the app. That generated config is in a read-only filesystem. It sounds weird at first, but it has a lot of advantages which is not the point here, so I won't say any more.

I have to say my first time setup was quite rough, so here's some constructive feedback:

the config docs don't mention what the defaults are so it's really hard to know what to set/override, and what format is expected
the config docs has sections, but the config file is not supposed to have them I guess having a config file with all defaults would be quite useful for this and the above point
current release ships with broken INI parsing. This wasted a LOT of my time: some settings were just being ignored, but others not, and there were no logs/errors to indicate anything
the bug fixed in efd7838b02f30b3c99611fc16c3f05a95fe8aadf also took me quite some time to realize what was happening

I went with minimal changes, but TBH after spending a lot of time looking at the code I'm under the impression it would need a lot of reworking. There's a lot of custom code (which is fun to do, and I totally understand the want), but I think the consequence is everything is not as polished as it could be if you relied more on standard/library solutions.
The INI thing is a good example of that IMO. But even more generally, rolling your custom crypto, custom config code, etc. ends up adding a lot of bugs where the python ecosystem already has great solutions :)

I hope this doesn't sound too harsh, I really appreciate all the work you've done, and the UX is most likely a lot better using the container. Just trying to give constructive criticism and feedback.

krateng / maloja

Misc. fixes from first use #328