Gerald Wiese <wi...@gnuhealth.org> writes: > Hi everyone, > the last years I put quite much effort into improving installation > related things here and there and thought that we would end up > synchronizing manual (Vanilla) and automated (Ansible) things. > Now I see much of my work, propositions and discussions discarded and > don’t really feel satisfied but rather reluctant to just automate the > result of todays Vanilla installation. > In the end we have a new interactive Python script with new complexity > but nobody joined to work on Ansible which was already rather too > complex than too simple and which is already THE Python thing to use > for creating directories, installing packages and so on. > > Furthermore I did not really see contributions, concrete feedback,
No feedback is a big problem, not just for ansible, but for all gnuhealth development. > opened issues or something similar regarding the system administration > gimmicks which I added on top of the automation of the installation. > > What I did today is to restore the last stable documentation that was > overwritten by outdated content and to push Ansible version 1.5.1 > which is still diverging from Vanilla Installation but running with > new PyPI versions of GH packages and some problems fixed that were > introduced from latest Ansible versions. > > Before I put more work I would like to have some honest feedback like > how much is the GH Ansible project actually used and how should it > develop? > > For example should it: > > A) Get dropped > > B) Just have Vanilla automated and tested but remove further features > > C) Automate Vanilla and continue as before with further features > > Let me know what you think please! > > Best > Gerald > --
