develop in prod has always used rsync, the difference is that now normal deploy also uses rsync. either way, both git and rsync will only push images the first time; you shouldn't have any problems there. the main thing is just the first time you clone on a new machine/push to a new server might be slow. Either approach is probably fine. as advantage of putting them in s3/digitalocean spaces etc is that the images will already be in a cdn, whereas if you put them in the repo and serve them with your biff app they'll load a bit slower for users.

though it's pretty easy to use E.g. https://images.weserv.nl/ to use your biff app as an origin for images and then cache/serve them through a cdn. so in conclusion, eh 🤷

Thanks. That was helpful. Good to know there are plenty of options, but the defualt is sufficient!