Lets go through these different files and folders and have a look what they are there for and what content they might contain.
cache - folder
The cache folder contains all the snippets that have been created with the tag <cfcache>.
cfclasses - folder
This is the folder that is used in order to store the .class files that Railo generates. It contains a folder for each mapping and inside this folder the sub directories of the original location of the compiled files are still maintained. The pattern of the directory looks like this:
CF{Foldername with replaced special chars}{Checksum}. So files from D:\projects\mys\ land in this folder:
D:\Projects\mys\WEB-INF\railo\cfclasses\CFD__Projects_mys1496\
Inside this folder you will find that a file named index.cfm will turn into index_cfm$cf.class. So it is quite easy to see which file matches to which compiled pendant.
Small trick: If you take the file index_cfm$cf.class and rename it to index.cfm and replace the original one in the folder d:\projects\mys then the application will still run and your code is protected. The most important thing is that it must not be named different (like index1.cfm) or it will not work.
classes - folder
Here you can place Java classes that should be loaded at startup for this particular web context.
client-scope folder
This folder contains different files that contain the client scope of users if you choose to use type "file" when defining the client scope usage in the <CFAPPLICATION> tag.
customtags - folder
This is the default custom tag folder for the web context. It is by default defined in the Railo Server Administrator and therefore defined in each web context.
lib - folder
Here you can place Java JAR files that should be loaded at startup for this particular web context.
library - folder
If you have your own JSP or Railo tag or function libraries written in Java and you place a corresponding fld or tld file inside the fld or tld directory these tag or function libraries are loaded at startup and you do not have to load them on each page you need them with <CFIMPORT>. In addition the descriptions will be available in the Railo Administrators under Documentation.
Since Railo 3.1 inside the library folder there are two new directories called tag and function which allow you to extend Railo's functionality for this web context with your own tags and functions written in Railo CFML. There are several guides in the Railo blog that explain how this works. You in fact just need to copy the corresponding custom tag into the tag directory or the .cfm template containing the functions in the function directory and then restart the engine. Then you can use them as internal tags or functions.
logs - folder
The logs directory contains all Railo generated log files. The log files generated are:
| File name | Description |
| mail.log | Contains the log for the mail handling |
| scheduler.log | Log for scheduled tasks |
| application.log | Contains the messages of errors of the web context |
| exception.log | Contaisn the fill messages including the details |
| trace.log | When you use the tag CFTRACE the result will be stored here as well |
| requesttimeout.log | This file saves all requesttimeouts occuring in the web context |
remote client - folder
This folder contains all failed Railo tasks. The ones that still are going to be retried are stored in the subfolder open and the ones that have failed until the last retryevent has occured are stored in the closed folder. This ensures that the tasks survive even server crashes or restarts.
scheduler - folder
When you define scheduled tasks they will be defined in the file scheduler/scheduler.xml. So this might be a file to backup as well.
search - folder
Just like the scheduler folder the search folder contains the search.xml that holds all collections defined for this web context. This file (together with the index files) should be backed up as well.
storage - folder
If you store data inside a plugin, it will be stored in this folder.
temp - folder
The temp folder us used to temporary store files that are uploaded to the web server. It need write permissions in order for the CFFILE action="upload" tag to work properly.
video - folder
The video folder is used by the paid extension for the CFVIDEO tag. it contains a XML file with different settings as well as some folders with the necessary binary files.