Source-less Deployment of Coldfusion

Best Practices , ColdFusion , Tips and Tricks Add comments

When deploying applications to any 3rd party hosting provider or client, you may wish to consider protecting your development effort and intellectual properties (IP) by either encrypting or pre-compiling the application code.

In the attached document, I will briefly cover a number of ways in which you can accomplish this.

There are currently three methods of deploying your ColdFusion applications in an encrypted format, which ship with ColdFusion, so as to help protect your code:

   1. Encrypting templates using the “cfencode” utility.
   2. Pre-compiling and deploying templates as Java Byte code using the “cfcompile” utility.
   3. Deployment Packages as J2EE Archives (EAR or WAR files) – accomplished using the ColdFusion Administrator.

Another option is packaging your application in ColdFusion Archive Files (CAR), but this is not within the scope of this document as there is no compilation or encryption used with this method.

Further details can be found at:

The above options all have their own behaviours, pros and cons.  These are discussed in more detail below.

The document can be downloaded from here.

If anyone has anything to add, please feel free to contact me or comment below.


Bookmark and Share

0 responses to “Source-less Deployment of Coldfusion”

Leave a Reply

Leave this field empty:

Powered by Mango Blog. Design and Icons by N.Design Studio