Organizing custom files

We recommend creating a separate folder for your customized files, rather than placing them alongside the original ones. This approach offers two key benefits:

• Easier Reversion: You can quickly revert to the original interface configuration if needed.

• Upgrade Protection: Your custom files will remain intact after version upgrades.

You can choose to store the customized files either within or outside the web directory. Here’s how each option behaves differently:

Storing Customized Files Inside the Web Directory

If the custom directory is created within the web directory:

1. The files can be accessed externally via a URL, such as: https://127.0.0.1/BrandingFiles/customizedFile.html.

2. Paths in the WebAliases.ini file can be relative to the web directory. For example:

   /img/ThinRDPSmall.png=BrandingFiles\MyLogo.png

Check the sections on Changing the Logo and Customizing Web Files for additional examples of relative paths.

Storing Customized Files Outside the Web Directory

Alternatively, you can place the customized files in any other directory on your disk. In this case:

1. The files will be more secure, as they won’t be accessible via URL.

2. Paths in the WebAliases.ini file must be absolute. For example:

   [Alias]
   /index.html=c:/BrandingFiles/my_index.html
   /images/ThinRDPSmall.png=c:/BrandingFiles/MyLogo.png