Oops, sorry Mathias, I didn' intend to be rude. Please don't feel offensed. My concern was about JJ question, not about the content of the page.
Talking here about this page, is a bit off-topic but I think better here than nothing. <off-topic> I admit I should have contributed. Because I endlessly answered the same questions about installation, I maintain a script to automate it and found easier to maintain a script than a documentation. Nevertheless, I don't need to be convinced that understanding is better than launching a script and a Debian installation documentation makes sens. When you install Trytond on a Debian server, you need to - install postgresql and configure it - install "external applications" like UNO and probably LibreOffice - install Trytond software, modules and their dependencies We may agree on a safe process to do it and get a working server. At the end of the document, I read "It is highly recommended to run pip on Debian systems in a virtual environment. You have been warned." I share this point of view, and think this is the process we should describe first in beginner's installation documentation JJ asked for. Probably a list of the commands we use during this process would help. I have no opinion about packages because I don't use them. I'm afraid of an unsafe installation to run trytond as root and of automated package updates, out of my control. Am I right ? And I think pip is more stable and predictable than hg repositories which will be the option for developpers, but this is another story. </off-topic> After a second thought, I am reconsidering my initial point of view, and I think we should improve access to documentation, even when this documentation can still be improved. If you think that a wiki can be phased with software versions, as an installation manual must be, then it is maintainable for me and I have no more concern on the issue. Regards
