Hey, thanks for your input!
> given we can get it working properly
I think thats a big part of the "soft skills" that the ones that cannot contribute directly to the code (like us) can deal with. We can write documentation. You're already doing it! We could be working together on this in collaboration with the developers if we were organised together.
> Sadly, I'm on my own to administer the foodcoop's server ... The development of the YunoHost instance looks like a good answer to that issue.
Same. I am the one who packaged Foodsoft on YunoHost but unfortunately, I starting to realise that it is very hard to configure and maintain. I also have the feeling that the Docker solution is "the one" that should be focused on since a lot of the other coops use it. So, I will probably deprecate the YunoHost packaging soon.
> I'm actively working on a complete step by step guide to install foodsoft, adapted to docker beginners, like I am. It is nearly done for basic docker installation process, just missing a proper emails configuration. Some help about it would be greatly appreciated btw.
TBH, I am also thinking of moving to the Docker setup in order to resolve the quite difficult configuration issues with my own setup. I see that https://github.com/foodcoops/foodcoops.net
is probably a good base to work from but I have not got so far as to try it yet.
Again, I think this ties into project sustainability topic as a whole.