The wiki provides quite some details already, but we haven't kept the information up to date and are also lacking a concise summary and more details here and there.
The goal here is to provide sufficient instructions for setting up the requirements for using the stack for anyone new to the project (i.e. w/o asking around).
:information_source: This issue might be partially obsolete assuming we have sufficiently embraced 'configuration as code', which would imply resp. requirements to be implicitly documented therein. Regardless, it is common for a software stack this size to have a dedicated requirements section in the docs.
The wiki provides quite some details already, but we haven't kept the information up to date and are also lacking a concise summary and more details here and there.
The goal here is to provide sufficient instructions for setting up the requirements for using the stack for anyone new to the project (i.e. w/o asking around).
:information_source: This issue might be partially obsolete assuming we have sufficiently embraced 'configuration as code', which would imply resp. requirements to be implicitly documented therein. Regardless, it is common for a software stack this size to have a dedicated requirements section in the docs.