Ansible - Provide documentation

[C0nsultant]

• short overview over the role in ansible/README.md
• explain setup instructions in docs/setup.rst

[jonaswinkler]

I'm not sure whether that's needed; the default master branch always reflects the latest release, as far as functionality is concerned. I push functional changes and additions to dev, and they only get into master as part of a new release.

[jonaswinkler]

How would I go about updating paperless when I installed it with ansible?

[C0nsultant]

How would I go about updating paperless when I installed it with ansible?

The simple answer: You just update paperlessng_version in your ansible configuration and run the role again.

The honest answer: Above approach works when the bare-metal deployment process does not change between releases. If it does, the role has to be updated accordingly. This also means that the user will have to download the newest version of the role (hencewhy I stated in the documentation to checkout the newest release, which should include a working ansible role for that release).
The other option is to modify the role such that installation of any version is supported (i.e. incorporate steps specific to individual releases - compiling the frontend for example used to be required, but now is not anymore). This would be the cleanest solution to ship to people, but of course also the one hardest to maintain... really not sure.