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.
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:
| Field | Description |
|---|---|
| Name | A human-readable display name |
| Handle | A DNS-1123-compliant identifier (immutable after creation) |
| Content | The raw text content (no syntax check) |
| Content length | The size of the content in bytes |
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, the mount path you choose is the exact file the content is delivered as -- not a directory. Enter the full file path your application expects:
/etc/nginx/conf.d/site.conf # the mount path IS the fileThe file is placed at exactly that path and sits alongside the other files your image already ships in that directory -- it does not replace or hide them.
Rotation
Rotation creates a new version of the config. The previous version is retained for rollback. After rotation:
- Because the config is mounted as a single exact file, the running container does not pick up the new version automatically. Use the Redeploy button on the Consumers panel to roll the container onto the rotated version.
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.