Notifications Service Configuration
Introduction
The Infinite Scale Notification service provides …
Services are under development because of the |
Configuration
Environment Variables
The notifications
extension is configured via the following environment variables:
Name | Type | Default Value | Description |
---|---|---|---|
|
string |
The log level. Valid values are: "panic", "fatal", "error", "warn", "info", "debug", "trace". |
|
|
bool |
false |
Activates pretty log output. |
|
bool |
false |
Activates colorized log output. |
|
string |
The path to the log file. Activates logging to this file if set. |
|
|
string |
127.0.0.1:9174 |
Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed. |
|
string |
Token to secure the metrics endpoint |
|
|
bool |
false |
Enables pprof, which can be used for profiling |
|
bool |
false |
Enables zpages, which can be used for collecting and viewing in-memory traces. |
|
string |
127.0.0.1 |
SMTP host, to connect to. |
|
string |
1025 |
Port of the SMTP host, to connect to. |
|
string |
Sender of emails, that will be sent. |
|
|
string |
Password of the SMTP host, to connect to. |
|
|
string |
127.0.0.1:9233 |
Endpoint of the event system. |
|
string |
ocis-cluster |
Cluster ID of the event system. |
|
string |
notifications |
Name of the event group / queue on the event system. |
|
string |
127.0.0.1:9142 |
CS3 gateway used to look up user metadata |
|
string |
Machine auth API key used for accessing the 'auth-machine' service to look up their email. |
Since Version: +
added, -
deprecated
YAML Example
# Autogenerated
# Filename: notifications-config-example.yaml
log:
level: ""
pretty: false
color: false
file: ""
debug:
addr: 127.0.0.1:9174
token: ""
pprof: false
zpages: false
notifications:
SMTP:
smtp_host: 127.0.0.1
smtp_port: "1025"
smtp_sender: noreply@example.com
smtp_password: ""
events:
endpoint: 127.0.0.1:9233
cluster: ocis-cluster
group: notifications
reva_gateway: 127.0.0.1:9142
machine_auth_api_key: ""