Clarify MinIO development settings

[astrojuanlu]

In #8082 (comment), @cocobennett followed the steps to configure MinIO for local development and still ended up with an incomplete environment. In fact, I had made the same mistake two weeks early when I just joined the company. @stsewd clarified later, but this should be present in the docs.

In particular, I think we should replace this:

https://github.com/readthedocs/readthedocs.org/blame/eb682d8b8f480e96e7478d968aa12e52f4118063/docs/development/install.rst#L66-L71

by something that doesn't assume that the user knows how MinIO works.

[astrojuanlu]

Also, instead of waiting for the first build to create the media bucket, we can either create it manually or automate it on init somehow. What do you think @stsewd @humitos?

[humitos]

instead of waiting for the first build to create the media bucket, we can either create it manually or automate it on init somehow

Yes. This is something we want to do. We used to do this when using Azurite (Azure Blob Storage emulator) but when we migrated to S3 we removed this because the bucket were automatically created on the first usage. However, that won't be true anymore when we upgrade django-storages. See readthedocs/common#80 (comment)

Summarizing, we want that feature back 😄

[astrojuanlu]

I opened #8113 to address this and other related doc improvements. However, I did not address the automatic creation of the media bucket (quickly tried locating the old create_container.sh without success).

[humitos]

However, I did not address the automatic creation of the media bucket (quickly tried locating the old create_container.sh without success).

This is the script I'm referring to https://github.com/readthedocs/common/blob/7c126c3ffa8a0314e92b3a026bcb73c1f1ba8526/dockerfiles/scripts/create-containers.sh

However, that script was done for Azurite Blob Storage (it uses the az command). The idea is exactly the same, but we will need to use AWS CLI instead. I may not be that easy 😄