I had a few ideas about how quickstart.sh could be enhanced, specifically around allowing it to be extended so that different "types" are supported and also how to make it easy for people to find them.
The main idea was:
Split out the quickstart functionality into scripts per "type", structurally similar to how the ADOP CLI works
Introduce a "community" folder or similar, so that unmaintained (in the sense that they don't have to be tested every time there is a change, for example if it's for an IaaS that we do not have access to) types can still reside in the repository and be immediately accessible to users
Each quickstart type would deploy ADOP using an appropriate CLI type (see #277)
I had a few ideas about how quickstart.sh could be enhanced, specifically around allowing it to be extended so that different "types" are supported and also how to make it easy for people to find them.
The main idea was:
I started doing this over here and would like to continue the idea, so thought about opening it up to the community for thoughts/questions on how it would work: https://github.com/nickdgriffin/adop-docker-compose/tree/feature/community_quickstart