Description

Decoupling setup process from setup.sh script by introducing a setup script inside the container that coordinates the setup process. This is not a breaking change. This way, we do not have to keep track of versions of setup.sh, which was said to be a no-no here. This is a blog post we're linking to in our documentation. This change brings the additional benefit for Kubernets users to be able to make use of setup now, without the need for setup.sh.

The maintainers discussion referencing / talking about the current setup.sh versioning-problem can be found here.

This PR was really made possible by @NorseGaud with #2134

Type of change

• Improvement (non-breaking change that does improve existing functionality)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (README.md or the documentation under docs/)
• If necessary I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes