# lanowl — every secret it holds, in config/secrets.yaml (mode 600). A new install writes its # own, and the dashboard sets each login and token in it (the first-run setup, Settings → # Secrets) without ever showing one again. This file shows the format, to edit it by hand. # # Never in config.yaml or inventory.yaml, so those two can be shared or versioned. Read again # whenever it changes: an updated password or token needs no restart (a password that becomes # a key does: restart lanowl). A password reaches ssh through SSH_ASKPASS and sudo through # stdin — never argv, a log line, a message, or the model. `lanowl --check` says where each # secret comes from, and what is missing, never a value. # Named logins; several devices may share one. Each has a user and: # password: "..." ssh with a password (routers, cameras, most appliances) # key: true lanowl's own ssh key (`ssh_key` below) — or key: /path/to/key # key + password the key logs in, the password is what sudo asks for # A user other than root needs sudo for what reads or changes the system: with a password, # sudo takes it; with a key only, a NOPASSWD rule (for `restart`, one for exactly # `systemctl restart ` is enough). logins: routers: {user: admin, password: "change-me"} server: {user: root, key: true} cameras: {user: admin, password: "change-me"} # mac: {user: you, key: true, password: "change-me"} # vps: {user: root, key: true} # lanowl's own logins, named in config.yaml: the router's read-only user, for its API and # REST (mikrotik.credentials — give it a group with read rights only), and the MQTT # broker's (mqtt.credentials), if it wants one router-read: {user: lanowl, password: "change-me"} # mqtt: {user: lanowl, password: "change-me"} # Address -> login name, for devices that do not name theirs in the inventory # (`credentials:`, which wins over this map). devices: # 192.168.88.30: server # The services lanowl talks to. tokens: telegram: "" # the bot's token, from @BotFather # homeassistant: "" # a long-lived access token (your HA profile → Security) # webhook_url: "" # where the webhook posts: https://host/path (a secret, it often carries a key) # webhook: "" # a bearer token for it, only if its receiver wants one # lanowl's own ssh key, for every `key: true` login. Make one with # ssh-keygen -t ed25519 -N '' -C lanowl -f config/id_ed25519 # and put config/id_ed25519.pub in each such device's authorized_keys. ssh_key: /config/id_ed25519 # Instead of this file, a deployment may give lanowl's own secrets in the environment: # LANOWL_TG_TOKEN, LANOWL_HA_TOKEN, LANOWL_WEBHOOK_URL, LANOWL_WEBHOOK_TOKEN, # LANOWL_MIKROTIK_USER / _PASS, LANOWL_MQTT_USER / _PASS, # LANOWL_SSH_KEY (a path). Each but the key also as _FILE, a file holding the value: how # Docker secrets arrive (/run/secrets/). The variable wins, then its _FILE, then this file.