Configuration
It is possible to configure aha-secret by setting environment variables.
Environment Variables
The following environment variables can be set to configure the application:
Variable | Description | Default |
---|---|---|
URL | Add url as origin | base-url |
SESSION_SECRET | Set custom session-secret | random |
MEMCACHE | Set a memcache-server and enable rack-attack | empty(disable rack-attack) |
APP_LOCALE | Set the locale for the application | empty (default is en) |
PLAYWRIGHT_HEADLESS | Run e2e tests with playwright headless |
Custom Style
The application can be customized by changing the following files:
- ‘config/config.yml’ - set ‘custom_stylesheet’ to true
- ‘public/custom.css’ - add your custom css to this file
See the file ‘public/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/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;
}