XConfig delivers a file to an application’s container. Use it for configuration such as a web server config; use a volume for mutable business data.
Upload a file
Open a supported application’s configuration files, select a local file, and choose an absolute container file path. The file must be nonempty and no larger than 1,023,999 bytes. The target path is 2–255 characters and must not end in /.
For example, an Nginx configuration can target:
/etc/nginx/conf.d/default.confConfirm that the image reads that path and that the content is valid for its installed version.
Visibility and lifecycle
File contents can be downloaded by users with the relevant shared-read access. Do not assume arbitrary content is secret or automatically redacted.
Updates create replacement configuration content and update the application mount. They are not an in-place editing service for a writable file. Deleting or replacing configuration can affect subsequent tasks; inspect logs and a real request afterward.
Local-volume stateful applications use a different configuration mode and do not support XConfig. Choose the mode before creating the application.
Diagnose and continue
An invalid path, empty file, or oversized upload is rejected. A running container may still fail to use the file if the image expects another path or the configuration is invalid. Check startup logs and the image documentation.
Mounting and updating configuration explains replacement and target-path changes. Persistence explains where to store writable data.