Configuration
It is possible to configure aha-secret by setting environment variables.
Environment Variables
The application is configured using environment variables. Use the new AHA_SECRET_* variables for all new deployments. Deprecated variables are supported for backward compatibility but should be avoided.
The following environment variables can be set to configure the application:
| Variable | Description | Default |
|---|---|---|
| AHA_SECRET_BASE_URL | Set base-url of Website. | / |
| AHA_SECRET_PERMITTED_ORIGINS | CORS/CSRF allowed origins | (none) |
| AHA_SECRET_SESSION_SECRET | Set custom session-secret | random |
| AHA_SECRET_MEMCACHE_URL | Set a memcache-server and enable rack-attack | empty (disable rack-attack) |
| AHA_SECRET_APP_LOCALE | Set the locale for the application | (none) |
Complete Environment Variables Reference
The following environment variables can be used to configure aha-secret. Most can be set in your shell, .env file, or via your deployment platform.
| Variable | Description | Default | Config.yml Key | Notes |
|---|---|---|---|---|
AHA_SECRET_BASE_URL | Set base-url of Website. | / | base_url | |
URL | (Deprecated) Old permitted origins variable | (none) | permitted_origins | Use AHA_SECRET_PERMITTED_ORIGINS instead |
AHA_SECRET_MEMCACHE_URL | Memcache server URL for rate limiting and caching | (none) | memcache_url | Recommended. Enables Rack::Attack. Example: localhost:11211 |
MEMCACHE | (Deprecated) Old memcache server variable | (none) | memcache_url | Use AHA_SECRET_MEMCACHE_URL instead |
AHA_SECRET_SESSION_SECRET | Secret for session encryption | Random | session_secret | Set for production deployments |
SESSION_SECRET | (Deprecated) Old session secret variable | Random | session_secret | Use AHA_SECRET_SESSION_SECRET instead |
AHA_SECRET_CLEANUP_SCHEDULE | Cron/interval for background cleanup | 10m | cleanup_schedule | Example: 1h, 5m |
AHA_SECRET_RATE_LIMIT | Requests per period per IP | 65 | rate_limit | Used by Rack::Attack |
AHA_SECRET_RATE_LIMIT_PERIOD | Rate limit period (seconds) | 60 | rate_limit_period | Used by Rack::Attack |
AHA_SECRET_DEFAULT_LOCALE | Default locale | en | default_locale | |
AHA_SECRET_MAX_MSG_LENGTH | Max message length | 20000 | max_msg_length | |
AHA_SECRET_PERMITTED_ORIGINS | CORS/CSRF allowed origins | (none) | permitted_origins | |
PERMITTED_ORIGINS | (Deprecated) Old CORS origins variable | (none) | permitted_origins | Use AHA_SECRET_PERMITTED_ORIGINS instead |
AHA_SECRET_APP_LOCALE | Force app locale | (none) | (none) | Overrides default_locale when set |
APP_LOCALE | (Deprecated) Old app locale variable | (none) | (none) | Use AHA_SECRET_APP_LOCALE instead |
RACK_ENV | Rack environment | development | (none) | Use production for deployment, test for tests |
SKIP_SCHEDULER | Disable background scheduler (Rufus) | (none) | (none) | Set to true in test/CI |
COVERAGE | Enable code coverage (SimpleCov) | (none) | (none) | Used in test/CI |
CI | Set automatically in CI | (none) | Used to enable CI-specific logic | |
SHOW_BROWSER | Show browser in e2e tests | (none) | Set to true to see browser window | |
undercover_version | Used in CI for coverage matrix | (none) |
Deprecated Environment Variables
MEMCACHE,SESSION_SECRET,APP_LOCALE,URL,PERMITTED_ORIGINSare deprecated. Use theAHA_SECRET_*equivalents.- Deprecated variables are still supported for backward compatibility but will show a warning.
Creating a config.yml File
The application can use a config/config.yml file for configuration instead of environment variables. This is useful for static deployments or when you prefer file-based configuration.
Sample config.yml
---
default: &common_settings
rate_limit: 65
rate_limit_period: 60 # in seconds
cleanup_schedule: "10m"
base_url: "/"
default_locale: "en"
max_msg_length: 20000
session_secret: "your-secret-key-here"
memcache_url: "localhost:11211"
permitted_origins: "http://localhost"
custom:
stylesheet: true
html_title: false
html_title_string: "Share secrets encrypted"
meta_description: false
meta_description_string: "Share secrets encrypted"
meta_description_keywords: "Share, Secrets, Encrypted"
footer: false
footer_string: '<p>Custom footer <a href="https://example.com">link</a></p>'
development:
<<: *common_settings
session_secret: "dev-secret"
memcache_url: ""
permitted_origins: "http://localhost:9292"
production:
<<: *common_settings
session_secret: "CHANGE-THIS-TO-A-SECURE-RANDOM-STRING"
memcache_url: "memcached:11211"
permitted_origins: "http://localhost"
test:
<<: *common_settings
session_secret: "test-secret"
memcache_url: ""
permitted_origins: ""
max_msg_length: 1000
Configuration Notes
- session_secret: Should be a long, random string for production
- memcache_url: Leave empty to disable rate limiting, or set to your memcache server
- permitted_origins: Set to your domain for CORS/CSRF protection
- Environment-specific sections: Override common settings per environment
- custom: Configure UI customization options
Precedence and Override Logic
- Environment variables override values in
config/config.yml. - If neither is set, built-in defaults are used.
- Deprecated ENV vars are mapped to new ones with a warning.
Test/CI-Specific Variables
SKIP_SCHEDULERis set totruein test/CI to disable background jobs.COVERAGE,CI,SHOW_BROWSERandundercover_versionare used for test and CI configuration.
Disabling Background Jobs
Set SKIP_SCHEDULER=true to prevent Rufus::Scheduler from running background jobs (e.g., in test or CI environments).
Custom Style
The application can be customized by changing the following files:
- ‘config/config.yml’ - set ‘custom_stylesheet’ to true
- ‘public/stylesheets/custom.css’ - add your custom CSS overrides here
See the file ‘public/stylesheets/application.css’ for defined css classes you could simply overwrite.
You can even add your own logo by copying a logo to the ‘public’ folder and setting a background image in the ‘public/stylesheets/custom.css’ file.
Example:
div#logo {
width: 200px;
height: 40px;
background-image: url('logo.png');
position: fixed;
left:5px;
top:5px;
max-width:100%;
background-repeat: no-repeat;
}
Reverse-Proxy
The following nginx-config example can be used for a reverse-proxy:
server {
root /var/www/html;
# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;
server_name <YOUR_DOMAIN>;
location / {
# USE THE FOLLOWING HEADERS TO PROVIDE THE
# REAL IP SO THAT RATELIMIT WORKS PROPERLY
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-Proto https;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Host $remote_addr;
proxy_pass http://127.0.0.1:9292;
}
listen [::]:443 ssl http2;
listen *:443 ssl http2;
ssl_certificate <PATH_TO_YOUR_CERTIFICATE>;
ssl_certificate_key <PATH_TO_YOUR_PRIVATE_KEY>;
ssl_dhparam <PATH_TO_YOUR_DHPARAMS>;
# HSTS
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
}