Data in configuration files

Config templates

A template of such config file should be kept in the repository with keys masking the sensitive data. Next, you can use the Find & Replace action before the deployment to update the data in the template.

You should keep your configuration template in the repository. In the template instead of providing sensitive data provide keys. Then replace the data in the template just before the deployment using the Find & replace action. Such file can be safely deployed to the server:

Find and Replace action configuration

Uploading config to filesystem as static file

In some cases, you may not want to store your config in the repository, but still want to deploy it with the rest of the source files. To do this, you can manually upload the file to the filesystem as a static file:

Filesystem tab

To ensure only authorized users have access to the file’s content, you can restrict its permissions to specific users in the Permissions tab in the pipeline settings.