I've noticed that the application seems to assume that the site is hosted on the domain root (example.com) rather than using a subdomain (www.example.com)
As such, when enabling R2 for media on a subdomain, the suggested domain is media.www.example.com
This isn't really a problem - I spotted it and changed it before continuing.
However, when disabling R2 for media when testing something, then re-enabling it, it defaulted back to media.www.example.com which I didn't immediately pick up and so ended up having to clean up the extra sub-subdomain created in my DNS and R2 configuration.
Can I suggest that:
As such, when enabling R2 for media on a subdomain, the suggested domain is media.www.example.com
This isn't really a problem - I spotted it and changed it before continuing.
However, when disabling R2 for media when testing something, then re-enabling it, it defaulted back to media.www.example.com which I didn't immediately pick up and so ended up having to clean up the extra sub-subdomain created in my DNS and R2 configuration.
Can I suggest that:
- if the site uses the www subdomain, you default to dropping www before adding media to the front, and
- you somehow store the media domain chosen when initially enabled, and use that stored value as the domain when re-enabling R2 to ensure consistency
