This functionality was introduced in FarCry 6.2.0.
The CDN functionality encompasses many changes. Broadly speaking it is the ability to store and serve "transitory" files (e.g. CSS, images, etc) from somewhere besides the application server. Previously, FarCry's support for this kind of thing has been limited to configuring where on the web server files are stored.
The following use cases should now be supported:
- using local file system, S3, and FTP storage interchangeably
- configuring the 4 broad "types" of FarCry files separately (cache, images, secure files, public files)
- migrating files from an existing location to a new location
These changes introduce the idea of a "location", which is a discrete configuration that is later referred to by name. FarCry core uses five locations (cache, images, privatefiles, publicfiles, archive), and you should consider their access characteristics when you're looking at moving to a CDN - you may decide that some of these locations shouldn't be on a CDN because of security, serving responsiveness or file access speed.
media for archived records
Location | Used For | Access |
---|---|---|
cache | minified JS and CSS | Write once, served immediately, files are never changed, needs to be served quickly |
images | image formtool | Write once or twice (when resizing), read several times as source for different sizes, needs to be served quickly |
privatefiles | file formtool (secured and draft content) | Moved in and out as content is published and unpublished, needs to be able to be served in a controlled fashion |
publicfiles | file formtool (unsecured and approved content) | Moved in and out as content is published and unpublished |
archive | Write once, rarely read, doesn't need to be served at all |
To change FarCry's default behaviour you would override one (or all) of these in /projects/yourproject/config/_serverSpecificVarsAfterInit.cfm.
For more details on implementing FarCry CDN features:
Migrating an Existing Application to a CDN
This is a staged process designed to keep the site available as much as possible.
Stage 1: Preparing the Code
Most CDNs serve content from a domain other than the application one (the "local" CDN being the obvious exception). In many cases FarCry will take care of using the relevant domain automatically, but there are two cases where you may be referring directly to a file in your own code: files and images. You will need to make the following changes to prepare to a CDN that isn't on the same domain as the application:
files
All files should be linked to via /download.cfm, where FarCry will take care of file security and location. The format for these links is:
/download.cfm?downloadfile=[content objectid]&typename=[content typename]&fieldname=[file field]
images
Images in code should either:
- be prefixed with the result of application.fapi.getImageWebRoot(); or
- use the path returned from application.fc.lib.cdn.ioGetFileLocation() (see below)
Stage 2: Migrating Existing Files
- In /projects/yourproject/config/_serverSpecificVarsAfterInit.cfm add the new CDN. In Stage 3 you will be making it the default for core locations, but first you need to add it as a new location. This way you can copy existing files to it while still serving them from the old location. Refer to CDN Types above to see examples of this. Remember to name your new locations something non-standard (like new-images).
- After updating your application, open the CDN Migration Tool (Webtop -> Admin -> Developer Utilities -> Diagnostics -> CDN Migration Tool). Select the old and new locations and click Compare. NOTE: you will need to enter filter by /images for the images location.
- Select the files you want to upload and click Copy Files
It's a good idea to lock down content with your admin users during Stages 2 and 3. If you can't do this, you will have a period during Stage 4 where some files aren't available to users.
Stage 3: Switching the Application to the CDN
Go back to /projects/yourproject/config/serverSpecificVarsAfterInit.cfm and update the CDN locations with the core names. Update the application.
Congratulations! Your application is now serving content from the CDN!
If you couldn't lock down content during Stages 2 and 3, you should make sure to keep the default configs available (see CDN Types examples) and go on to Stage 4.
Stage 4: Cleaning Up Files Uploaded During Migration (optional)
This stage is only necessary if you couldn't lock down content during the migration. In this case you should now have the core locations using your CDN, and some non-standard locations that still refer to the old locations.
Now you can use the migration tool (from Stage 2) to copy missing files. The tool will highlight files that are already there and those that aren't.
Accessing CDNs in Your Own Code
There are situations where you will want to access the CDNs yourself for custom functionality. A couple of cases where we've done so:
- automatically generating archvies and uploading them to S3
- writing a migration utility to compare two CDN locations and copy selected files between them
- clearing out a CDN after doing tests on stage
This section describes the public API of the CDN library, which takes care of things like ensuring filename uniqueness, figuring out how to move files between different CDNs, and handling user uploads. Note that ALL public functions are prefixed with "io" to avoid conflicts with existing CFML functions.
You can access these function at application.fc.lib.cdn.
ioFileExists
Argument | Description |
---|---|
location REQ | The location to check. |
file REQ | The file to check. |
Does what it says on the box. Checks a single location to see if a file exists.
<cfif application.fc.lib.cdn.ioFileExists(location="cache",file=sCacheFileName)> <cfreturn sCacheFileName /> </cfif>
ioFindFile
Argument | Description |
---|---|
locations REQ | A list of locations to search. |
file REQ | The file to find. |
Searches the provided locations, and returns the first that contains the specified file, or an empty string if there isn't any.
<cfset currentLocation = application.fc.lib.cdn.ioFindFile(locations="privatefiles,publicfiles",file=arguments.stObject[arguments.stMetadata.name]) />
ioGetUniqueFilename
Argument | Description |
---|---|
locations REQ | A list of locations that the filename needs to be unique among. |
file REQ | The file to update. |
Returns a version of the specified filename which is unique among every listed location by appending numbers to the name. Note that it is rare to have to call this function directly, as all functions which put a file into a CDN have options to enforce filename uniqueness. However if you wish to change how FarCry enforces uniqueness, you can override this function in your project.
<cfset moveto = ioGetUniqueFilename(locations="privatefiles,publicfiles",file=newfile) />
ioGetFileSize
Argument | Description |
---|---|
location REQ | The location to check. |
file REQ | The file to inspect. |
Returns the size of the file in bytes.
<cfoutput>Size: <span class="image-size">#round(application.fc.lib.cdn.ioGetFileSize(location="images",file=arguments.stMetadata.value)/1024)#</span>KB</cfoutput>
ioGetFileLocation
Argument | Description |
---|---|
location REQ | The location to check. |
file REQ | The file to return. |
Returns serving information for the file. The result is a struct - either: method=redirect + path (URL) OR method=stream + path (local path).
<cfset stImage = application.fc.lib.cdn.ioGetFileLocation(location="images",file=arguments.stMetadata.value) /> <cfoutput><img src="#stImage.path#"></cfoutput>
ioWriteFile
Argument | Description |
---|---|
location REQ | The location to write to. |
file REQ | The file to write to. |
data REQ | The data to write to file. |
datatype OPT | One of text, binary, and image. Defaults to text. |
quality OPT | This is only required for JPEG image writes. Defaults to 1. |
nameconflict OPT | One of makeunique and overwrite. Default is overwrite. |
uniqueamong OPT | In the case of makeunique, this is the list of locations that the file should be unique in. Defaults to the same as location. |
Writes the specified data to a file.
<cfset stResult.filename = application.fc.lib.cdn.ioWriteFile(location="images",file=filename,data=newImage,datatype="image",quality=arguments.quality,nameconflict="makeunique",uniqueamong="images") />
ioReadFile
Argument | Description |
---|---|
location REQ | The location to check. |
file REQ | The file to read. |
datatype OPT | One of text, binary, and image. Defaults to text. |
Reads from the specified file.
<cfimage action="info" source="#application.fc.lib.cdn.ioReadFile(location='images',file=stResult.value,datatype='image')#" structName="stImage" />
ioMoveFile
Argument | Description |
---|---|
source_location OPT | The location to move the file from. |
source_file OPT | The file to move. |
source_localpath OPT | The local file to move. |
dest_location OPT | The location to move to. |
dest_file OPT | The file to move to. Defaults to the same as source_file. |
dest_localpath OPT | The local file to move to. |
nameconflict OPT | One of makeunique and overwrite. Default is overwrite. |
uniqueamong OPT | In the case of makeunique, this is the list of locations that the file should be unique in. Defaults to the same as location. |
Moves the specified file between locations. Note that when moving a file between different CDN types, this function moves the file to the local temporary directory, then to the target location from there.
Note that while every argument is marked as optional, in practice you need:
- source_location and source_file OR source_localpath
- dest_location and dest_file OR dest_localpath
<cfset application.fc.lib.cdn.ioMoveFile(source_location="publicfiles",source_file=arguments.stObject[arguments.stMetadata.name],dest_location="privatefiles") />
ioCopyFile
Argument | Description |
---|---|
source_location OPT | The location to copy the file from. |
source_file OPT | The file to copy. |
source_localpath OPT | The local file to copy. |
dest_location OPT | The location to copy to. |
dest_file OPT | The file to copy to. Defaults to the same as source_file. |
dest_localpath OPT | The local file to copy to. |
nameconflict OPT | One of makeunique and overwrite. Default is overwrite. |
uniqueamong OPT | In the case of makeunique, this is the list of locations that the file should be unique in. Defaults to the same as location. |
Copies the specified file between locations. Note that when copying a file between different CDN types, this function copies the file to the local temporary directory, then moves it to the target location from there.
Note that while every argument is marked as optional, in practice you need:
- source_location and source_file OR source_localpath
- dest_location and dest_file OR dest_localpath
<cfset application.fc.lib.cdn.ioCopyFile( source_location="images", source_file=stLocal.stInstance.thumbnail, dest_location="archive", dest_file="/#stLocal.stInstance.typename#/#stLocal.stProps.archiveID#_thumb.#ListLast(stLocal.stInstance.thumbnail,'.')#" ) />
ioUploadFile
Argument | Description |
---|---|
location REQ | The location to upload to. |
destination REQ | The target location. This can be a directory (in which case the filename from the upload is used) or a specific filename. Note that if a specific filename is provided, the function will check that the upload has the same extension and throw an uploaderror if it doesn't match. |
filed REQ | The form post field. |
nameconflict OPT | One of makeunique and overwrite. Default is overwrite. |
uniqueamong OPT | In the case of makeunique, this is the list of locations that the file should be unique in. Defaults to the same as location. |
acceptextensions OPT | If this is provided, then the function will check the uploaded file extension. If the extension is invalid an uploaderror will be thrown. |
sizeLimit OPT | If this is provided, then the function will check the size of the uploaded file. If the size is too great an uploaderror will be thrown. |
Uploads the a file to the specified location.
<cfset stResult.value = application.fc.lib.cdn.ioUploadFile( location="securefiles", destination=arguments.stMetadata.ftDestination, field="#stMetadata.FormFieldPrefix##stMetadata.Name#New", nameconflict="makeunique", uniqueamong="privatefiles,publicfiles", acceptedextensions=arguments.stMetadata.ftAllowedFileExtensions ) />
ioDeleteFile
Argument | Description |
---|---|
location REQ | The location to delete from. |
file REQ | The file to delete. |
Deletes the specified file.
<cfset application.fc.lib.cdn.ioDeleteFile(location="images",file="/#arguments.stObject[arguments.stMetadata.name]#") />
ioDirectoryExists
Argument | Description |
---|---|
location REQ | The location to check. |
dir REQ | The directory to check. |
Checks that a specified directory exists. All functions which write to a CDN use this function to check whether the target directory needs to be created first.
<cfset application.fc.lib.cdn.ioDeleteFile(location="images",file="/#arguments.stObject[arguments.stMetadata.name]#") />
ioDirectoryExists
Argument | Description |
---|---|
location REQ | The location to check. |
dir REQ | The directory to check. |
Checks that a specified directory exists. All CDN functions which create a file already perform internal checks to find out if a directory needs to be created first. As a result, there is no example in core of a call to this function.
<cfif application.fc.lib.cdn.ioDirectoryExists(location="images",file="/#stMetadata.ftDestination#")> <!--- something here ---> </cfif>
ioCreateDirectory
Argument | Description |
---|---|
location REQ | The location to check. |
dir REQ | The directory to create. |
Creates the specified directory, including parent directories. All CDN functions which create a file already perform internal checks and create directories as necessary. As a result, there is no example in core of a call to this function.
<cfset application.fc.lib.cdn.ioCreateDirectory(location="images",file="/#stMetadata.ftDestination#") />
ioGetDirectoryListing
Argument | Description |
---|---|
location REQ | The location to query. |
dir REQ | The sub-directory to filter by. |
Returns a query containing the files under the specfied directory. The resulting query has a single field "file", which is the full path as would be passed into the other CDN functions. The results are recursive and do not include directories, except by implication.
It is worth noting that the "images" location is unusual in that it usually corresponds to the project WWW directory, and so a naive query to the "images" location will return everything in the webroot. In practice, listings of "images" should be filtered by /images.
<cfset qSourceFiles = application.fc.lib.cdn.ioGetDirectoryListing(location=form.source_location,dir=form.source_filter) /> <cfset qTargetFiles = application.fc.lib.cdn.ioGetDirectoryListing(location=form.target_location,dir=form.target_filter) /> <cfset stFound = structnew() /> <cfloop query="qSourceFiles"> <cfif not structkeyexists(stFound,qSourceFiles.file)> <cfset stFound[qSourceFiles.file] = 1 /> <cfelse> <cfset stFound[qSourceFiles.file] = stFound[qSourceFiles.file] + 1 /> </cfif> </cfloop> <cfloop query="qTargetFiles"> <cfif not structkeyexists(stFound,qTargetFiles.file)> <cfset stFound[qTargetFiles.file] = 2 /> <cfelse> <cfset stFound[qTargetFiles.file] = stFound[qTargetFiles.file] + 2 /> </cfif> </cfloop> <cfloop collection="#stFound#" item="thisfile"> <cfset queryaddrow(qFiles) /> <cfset querysetcell(qFiles,"file",thisfile) /> <cfset querysetcell(qFiles,"inSource",bitand(stFound[thisfile],1) eq 1) /> <cfset querysetcell(qFiles,"inTarget",bitand(stFound[thisfile],2) eq 2) /> </cfloop> <cfquery dbtype="query" name="qFiles">select * from qFiles order by file</cfquery>