To support the new salesforce environments (UAT, staging, production) we’ve added corresponding cloudinary folder names, and I went ahead and created some duplicate upload presets (311_uat and 311_staging) based on the 311_dev preset I think you were using. These will put new submissions into an appropriate folder, allowing us to easily delete all new images created in that environment if, say, we were going to re-initialize that environment. Cases that are imported / migrated into a dev/uat/staging environment will already arrive with images in the /production folder, so they won’t be duplicated, modified, or deleted.
The presets we’re using (boston-development, boston-uat, etc) are similar but include some transformations which force a resize and do some color / hue balancing as well. You’re welcome to use them (though the naming is a little different, as they have to map to our differently named environments) or copy over some of the transforms to your presets.
From Dave:
To support the new salesforce environments (UAT, staging, production) we’ve added corresponding cloudinary folder names, and I went ahead and created some duplicate upload presets (311_uat and 311_staging) based on the 311_dev preset I think you were using. These will put new submissions into an appropriate folder, allowing us to easily delete all new images created in that environment if, say, we were going to re-initialize that environment. Cases that are imported / migrated into a dev/uat/staging environment will already arrive with images in the /production folder, so they won’t be duplicated, modified, or deleted.
The presets we’re using (boston-development, boston-uat, etc) are similar but include some transformations which force a resize and do some color / hue balancing as well. You’re welcome to use them (though the naming is a little different, as they have to map to our differently named environments) or copy over some of the transforms to your presets.