Just to echo @gcrk's sentiments here, our install guides currently cover a lot of ground. The methods we list are:
- Quick install
- Mono-container Docker installation (soon to be removed)
- Multi-container Docker installation
- Manual Debian and Arch Linux installation
- Ansible role
From both a documentation and a development perspective, this is a lot of overhead. Our current Debian/Arch Linux setup guide is one of the longest and most complex items in our help center, and comes across a bit scatterbrained as it lists all possible approaches.
From a technical writing perspective, our responsibility is to document the "happy path" to an installation. As mentioned above, we should provide a single, project-sanctioned way to get the software up and running manually on Debian-based systems as an alternative to the preferred containerised and automated deployment methods. Users can still play around with installing the software on other systems using Git and non-systemd inits if they want to, but we can't anticipate everything in our documentation.
Ultimately, when a user comes to our documentation they need to be told:
- The supported distros
- The required software
- The steps to get the software installed
Currently, we are just trying to anticipate too many eventualiites.