Business use case
Hi, we're currently thinking about using Cloudinary to help serve/manage client branding assets.
As we have multiple testing and production environments, we were wondering what the best course of action was.
A single free account (at first) managing each environments in different directories ?
/library/static/images/...
/library/stage/client-1/images/...
/library/test/client-1/images/...
/library/preprod/client-1/images/...
/library/prod/client-1/images/...
Multiple free accounts (at first) managing each environment in their own account ?
account-stage/library/client-1/images/...
account-test/library/client-1/images/...
account-preprod/library/client-1/images/...
account-prod/library/client-1/images/...
account-prod/library/static/images/...
A single paid account managing each environment in different virtual environment ?
Not sure what that would look like
Are there any limitations that I'm not considering / things to think about ? What do people usually do when using cloudinary / assets CDN with multiple environments that may use different assets for different environments ? Thanks !
Comments
-
Hello flgraveline,
Great questions! My name is Teresa Gomez and I am a part of the sales organization here at Cloudinary. Please expect an email from Jared Vargas (jared.vargas@cloudinary.com) who will find a time to learn more about your use case in order to get your questions answered.
Cheers,
Teresa
0
