Plain Configs

A plain config stores arbitrary text content in the Bahriya platform. Use it for configuration formats Bahriya doesn't validate natively (.ini, .properties, .conf, custom DSLs) or any plain text file your application needs at runtime. The content is versioned and delivered to your containers as a mounted file.

When to use a plain config

• Your application reads configuration from a format Bahriya doesn't validate natively — .ini, .properties, .conf, nginx.conf, Apache config snippets, custom DSLs, license files
• You want the file to ship with your container without rebuilding the image
• You need the same file available across multiple containers or regions
• You want to version and roll back file changes

For YAML or JSON files, prefer YAML Configs or JSON Configs — they validate syntax on upload and catch typos before deploy.

What Bahriya stores

When you upload a plain config, Bahriya stores the content as-is without format validation:

Plain config content is shown back in the console, API responses, and CLI output.

Mounting in containers

When you attach a plain config to a container, you choose a mount path. The config file appears at:

<mount-path>/<filename>

Your application reads it from this path. For example, an Nginx container might reference /etc/nginx/conf.d/site.conf.

Rotation

Rotation creates a new version of the config. The previous version is retained for rollback. After rotation:

• File-mounted containers pick up the new config automatically within about 60 seconds. No manual action needed.
• If your application caches the file content in memory (Nginx, Apache, and similar daemons typically do), use the Redeploy button on the Consumers panel to force a restart.

Pricing

Plain configs are billed at $0.01 per month while they exist, plus $0.05 per region per month when attached to a project.

See also

• Deploy Plain Configs with Terraform
• Deploy Plain Configs with Reis (YAML Mode)
• Deploy Plain Configs with Reis (Flag Mode)