I think a better direction forward here is
As long as
asdfdoes not do
shimsfor ruby I am fine changing the official install script so it uses asdf which simplifies stuff for the end user. One less tool. @techAPJ we certainly need to make sure our setup stuff is under version control somewhere so people can contribute, is it?
The script can do fishing and install stuff via
portif you don’t have
If macports can not install something and you have no brew, just offer a BYO option.
I just see very high amounts of risk in an install guide that will certainly not withstand the test of time.
We maintain our Mac setup guide, we maintain our Docker setup guide. I have a guarantee this will happen cause we have paid staff doing this.
A third party guide may sort of work today, but on a long time scale will break, there is almost a 100% guarantee.
My strong preference here is to move our official setup script to a state where you could use it and build on it.
Then the howto becomes … “how to bring your own redis and pg when using the official mac install guide”