![]() ![]()
To separate your local assets from other environments, you can use the Cloudinary:UploadUrlPrefix app setting. Separating environments using URL prefixes If you don't want to use Cloudinary while developing locally, simply clear the Cloudinary:CloudName app setting. CLOUDINARY OPTIMIZE IMAGES FOR FREEYou can sign up for free at but you need a paid subscription for custom hostnames. Personally I use ngrok for setting up a reverse proxy, making my development machine website accessible over the internet. Testing locallyįor testing the Cloudinary integration locally, your website needs to be accessible over the internet via domain name or IP address (we can't use localhost for the mapping in Cloudinary). ![]() ![]() The URL must be accessible over the internet and should look like: the trailing slash). The URL prefix should be set to the absolute URL of the image provider's endpoint on your website. We need to configure Cloudinary for both these image providers by going to Settings > Upload in Cloudinary and specifying settings for Auto upload mapping:įolder should be set to the image provider name. If you have installed the Unsplash image provider as described in the Adaptive Images introduction, you will have two image providers registered: one called "episerver" for standard images uploaded in Episerver and one called "unsplash" for images originating from the Unsplash image service. The Adaptive Images add-on is based on image providers to allow for multiple image sources, such as DAMs or image services such as Unsplash.Įach image provider has a name which must be configured in Cloudinary so that it may fetch images to transform and optimize. The default matches the 25 megapixel limit of free Cloudinary accounts. CLOUDINARY OPTIMIZE IMAGES UPGRADEThe default matches the 10 MB limit of free Cloudinary accounts.Ĭloudinary:MaxDimensions is expressed in megapixels and should be changed if you upgrade your Cloudinary account to allow for higher image resolutions. Once installed, you should have a few more app settings in web.config: Ĭloudinary:CloudName should be set to the cloud name you selected when signing up for Cloudinary.Ĭloudinary:UploadUrlPrefix (optional) can be set to maintain individual collections of images in Cloudinary, for example to separate development, staging, and production environments, or to share a Cloudinary account for different websites altogether.Ĭloudinary:HostName can be changed if you sign up for a higher-tier Cloudinary account with a custom hostname.Ĭloudinary:PreserveTransparency should be set to true if you plan to use semi-transparent images and want to preserve the transparency in optimized/transformed images.Ĭloudinary:MaxFilesize is specified in KB and should be changed if you upgrade your Cloudinary account to allow for larger source images. CLOUDINARY OPTIMIZE IMAGES INSTALLInstall Cloudinary for the Adaptive Images add-on If you don't already have a Cloudinary account, go ahead and sign up for a free account.ĭuring sign-up, make note of your "cloud name" (and perhaps change it to something more memorable) as we'll need it for the configuration: Request one from if you don't already have one. ![]() CLOUDINARY OPTIMIZE IMAGES TRIALYou also need a developer license to trial the Cloudinary integration. You need an Episerver website with the Adaptive Images add-on installed, as described in the introduction to Adaptive Images. The Adaptive Images add-on for Episerver has native support for Cloudinary, to enable image optimization, transformation, and global CDN delivery. Note: This blog post assumes you've seen our introduction to Adaptive Images for Episerver. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |