Files¶
File objects represent uploaded files stored on the DRP server's managed filesystem. They provide a simple key-value store where the key is the file path and the value is the file content. Files are used for bootloader binaries, scripts, configuration files, and other static content needed during provisioning.
The DRP file server exposes these files over both TFTP and HTTP for
network boot and provisioning workflows. The filesystem space defaults to
/var/lib/tftpboot but can be overridden with the --file-root command
line flag (for example --file-root=$(PWD)/drp-data combined with
--isolated on install).
Files can be managed through the API (upload, retrieve, and delete) or by placing them directly into the file root directory for faster bulk loading. The TFTP and HTTP serving paths are read-only; modification must go through the API or direct filesystem access. This space is also used by the BootEnv import process when "exploding" an ISO to make its contents available to machines.
Unlike most DRP objects, File does not have a complex model structure with fields, metadata, or validation. It is a simple path-to-content mapping.
Note
Templates are not rendered to the file system. They are in-memory generated on the fly content.