mirror of
https://framagit.org/framasoft/framaspace/argos.git
synced 2025-04-28 18:02:41 +02:00
88 lines
2.5 KiB
YAML
88 lines
2.5 KiB
YAML
general:
|
||
db:
|
||
# The database URL, as defined in SQLAlchemy docs : https://docs.sqlalchemy.org/en/20/core/engines.html#database-urls
|
||
# Example for SQLite: "sqlite:////tmp/argos.db"
|
||
url: "postgresql://argos:argos@localhost/argos"
|
||
# You configure the size of the database pool of connection, and the max overflow (until when new connections are accepted ?)
|
||
# See https://docs.sqlalchemy.org/en/20/core/pooling.html#sqlalchemy.pool.QueuePool.params.pool_size for details
|
||
pool_size: 10
|
||
max_overflow: 20
|
||
# Can be "production", "dev", "test".
|
||
# If not present, default value is "production"
|
||
env: "production"
|
||
# to get a good string for cookie_secret, run:
|
||
# openssl rand -hex 32
|
||
cookie_secret: "foo_bar_baz"
|
||
# Default delay for checks.
|
||
# Can be superseeded in domain configuration.
|
||
# For ex., to run checks every minute:
|
||
frequency: "1m"
|
||
# Which way do you want to be warned when a check goes to that severity?
|
||
# "local" emits a message in the server log
|
||
# You’ll need to configure mail and gotify below to be able to use them here.
|
||
alerts:
|
||
ok:
|
||
- local
|
||
warning:
|
||
- local
|
||
critical:
|
||
- local
|
||
unknown:
|
||
- local
|
||
# Mail configuration is quite straight-forward
|
||
# mail:
|
||
# mailfrom: no-reply@example.org
|
||
# host: 127.0.0.1
|
||
# port: 25
|
||
# ssl: False
|
||
# starttls: False
|
||
# auth:
|
||
# login: foo
|
||
# password: bar
|
||
# addresses:
|
||
# - foo@admin.example.org
|
||
# - bar@admin.example.org
|
||
# Create an app on your Gotify server and put its token here
|
||
# See https://gotify.net/ for details about Gotify
|
||
# gotify:
|
||
# - url: https://example.org
|
||
# tokens:
|
||
# - foo
|
||
# - bar
|
||
|
||
service:
|
||
secrets:
|
||
# Secrets can be generated using `argos server generate-token`.
|
||
# You need at least one. Write them as a list, like:
|
||
# - secret_token
|
||
|
||
ssl:
|
||
thresholds:
|
||
- "1d": critical
|
||
- "5d": warning
|
||
|
||
# It's also possible to define the checks in another file
|
||
# with the include syntax:
|
||
#
|
||
# websites: !include websites.yaml
|
||
#
|
||
websites:
|
||
- domain: "https://mypads.example.org"
|
||
paths:
|
||
- path: "/mypads/"
|
||
checks:
|
||
- status-is: 200
|
||
- body-contains: '<div id= "mypads"></div>'
|
||
- ssl-certificate-expiration: "on-check"
|
||
- path: "/admin/"
|
||
checks:
|
||
- status-is: 401
|
||
- domain: "https://munin.example.org"
|
||
frequency: "20m"
|
||
paths:
|
||
- path: "/"
|
||
checks:
|
||
- status-is: 301
|
||
- path: "/munin/"
|
||
checks:
|
||
- status-is: 401
|