blossom environment:load_balancer:init
Create a starter load_balancer.yml for environment settings
Usage
blossom environment:load_balancer:init [--force]
Flags
| Flag | Description |
|---|---|
--force, -f |
Overwrite an existing starter file |
Examples:
blossom environment:load_balancer:init
blossom environment:load_balancer:init --force
Creates a starter load_balancer.yml for environment-scoped load balancer
settings.
Edit the generated file, then apply it with:
blossom environment:load_balancer:update --id environment-100 --data load_balancer.yml
The generated file is safe to apply unchanged:
load_balancer:
caddy_config:
basic_auth:
enabled: false
users: {}
Use caddy_config for a Caddyfile snippet inside this environment’s site block:
load_balancer:
caddy_config: |
header X-Environment production
Leave caddy_config blank to use Blossom’s managed routing defaults.
Basic Authentication is environment-scoped. Enable it with one or more users:
load_balancer:
basic_auth:
enabled: true
users:
reviewer: secret
owner: ${BASIC_AUTH_OWNER_PASSWORD}
Simple username: value entries are treated as plaintext passwords. To provide
a pre-generated BCrypt hash, use the explicit password_hash form:
load_balancer:
basic_auth:
enabled: true
users:
reviewer: secret
prehashed:
password_hash: $2a$12$gXQlFtKLQTrvHqqdNprFqOKANxADbYKN.DcVq4xsYJpvXeXFp8oJS
Disable Basic Authentication without removing the user list:
load_balancer:
basic_auth:
enabled: false
users:
reviewer: secret
owner: ${BASIC_AUTH_OWNER_PASSWORD}
Use environment variables for secrets. The CLI supports both $VAR and
${VAR} inside YAML files.
Blossom stores Basic Authentication passwords as BCrypt hashes. Passwords are write-only from the user’s perspective and are not returned by show commands.