Current Setup: Large CMS that has an "authoring" server and multiple "delivery" servers. Both the authoring and delivery servers are Windows servers running 64-bit Apache. The Apache Web root is setup on each server exactly the same--points to a directory on a SAN. The delivery servers are load balanced via another Windows server running Apache. I just finished setting up the ImageResizer server as a standalone image server and wanted to see what the best approach to getting the ImageResizer server to access and thus serve up the images.
So I guess the question is, what is the best way to allow the ImageResizer server access to the images that are part of a large CMS site? RemoteReader plugin? Setup the IIS site with the Web root as the same as the authoring and delivery servers? Any security issues with this approach? Any suggestions/alternate approaches?
Thank you!
If the SAN is well-behaved, SMB2 or later, and low-latency, you could mount the directory as a virtual folder within the IIS root (which you might want to keep separate).
For performance, it would be best to disable FCNMode - http://imageresizing.net/docs/v3/docs/fcnmode - particularly if you have lots of directories in the SAN.
Alternatively, you could use RemoteReader and point it to your Apache web servers, although you'll sacrifice the ability to update existing files (RemoteReader perma-caches everything to make performance reasonable).