Update Docker Compose Installation to Not Mount Config File as Read Only

[AML225]

Current Docker Compose examples state to mount the configuration file with the read-only flag (:ro). This prevents users from updating configuration using the new v12.0 UI functionality.

[netlify]

✅ Deploy Preview for frigate-docs ready!

Name	Link
🔨 Latest commit	83aa8b6
🔍 Latest deploy log	https://app.netlify.com/sites/frigate-docs/deploys/63b460bee7bcdb0008af0410
😎 Deploy Preview	https://deploy-preview-4871--frigate-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[NickM-27]

Maybe we should have it put :rw just so it's clear that this is the default?

[AML225]

Maybe we should have it put :rw just so it's clear that this is the default?

I'm not an expert on Docker volumes/bind-mounts, however the examples on https://docs.docker.com/storage/volumes/ and https://docs.docker.com/storage/bind-mounts/ seem to specify ":ro" when enforcing read-only, but don't specify anything when read-write. By default bind-mounts are read-write assuming there are no issues with user permissions (PUID/PGID).

[NickM-27]

Right, I was just suggesting that it would be more clear to frigate users that the config is read/write by default now. Then again if the user doesn't know the default the rw likely won't mean anything either so it's probably fine to leave it that way.