Files
spothole/config-example.yml
2025-11-26 07:40:46 +00:00

159 lines
4.1 KiB
YAML

# Config file example.
# Rename this to "config.yml" before running the software.
# Your callsign. Used to log into DX clusters and included in User-Agent when querying HTTP servers. Useful so if your
# server goes crazy and causes other people problems, they know who to contact :) If you don't have one, you can leave
# this as "N0CALL" and it shouldn't do any harm, as we're not sending anything to the various networks, only receiving.
server-owner-callsign: "N0CALL"
# Spot providers to use. This is an example set, tailor it to your liking by commenting and uncommenting.
# RBN and APRS-IS are supported but have such a high data rate, you probably don't want them enabled.
# Each provider needs a class, a name, and an enabled/disabled state. Some require more config such as hostnames/IP
# addresses and ports. You can duplicate them if you like, e.g. to support several DX clusters. RBN uses two ports, 7000
# for CW/RTTY and 7001 for FT8, so if you want both, you need two entries, as shown below.
# Feel free to write your own provider classes! There are details in the README.
spot-providers:
-
class: "POTA"
name: "POTA"
enabled: true
-
class: "SOTA"
name: "SOTA"
enabled: true
-
class: "WWFF"
name: "WWFF"
enabled: true
-
class: "WWBOTA"
name: "WWBOTA"
enabled: true
-
class: "GMA"
name: "GMA"
enabled: true
-
class: "HEMA"
name: "HEMA"
enabled: true
-
class: "ParksNPeaks"
name: "ParksNPeaks"
enabled: true
-
class: "ZLOTA"
name: "ZLOTA"
enabled: true
-
class: "WOTA"
name: "WOTA"
enabled: true
-
class: "APRSIS"
name: "APRS-IS"
enabled: false
-
class: "DXCluster"
name: "HRD Cluster"
enabled: true
host: "hrd.wa9pie.net"
port: 8000
login_prompt: "login: "
-
class: "DXCluster"
name: "W3LPL Cluster"
enabled: false
host: "w3lpl.net"
port: 7373
login_prompt: "Please enter your call: "
-
class: "RBN"
name: "RBN CW/RTTY"
enabled: false
port: 7000
-
class: "RBN"
name: "RBN FT8"
enabled: false
port: 7001
-
class: "UKPacketNet"
name: "UK Packet Radio Net"
enabled: false
-
class: "XOTA"
name: "39C3 TOTA"
enabled: false
url: "https://39c3.c3nav.de/"
# Fixed SIG/latitude/longitude for all spots from a provider is currently only a feature for the "XOTA" provider,
# the software found at https://github.com/nischu/xOTA/. This is because this is a generic backend for xOTA
# programmes and so different URLs provide different programmes.
sig: "TOTA"
latitude: 53.5622678
longitude: 9.9855205
# Alert providers to use. Same setup as the spot providers list above.
alert-providers:
-
class: "POTA"
name: "POTA"
enabled: true
-
class: "SOTA"
name: "SOTA"
enabled: true
-
class: "WWFF"
name: "WWFF"
enabled: true
-
class: "ParksNPeaks"
name: "ParksNPeaks"
enabled: true
-
class: "WOTA"
name: "WOTA"
enabled: true
-
class: "BOTA"
name: "BOTA"
enabled: true
-
class: "NG3K"
name: "NG3K"
enabled: true
# Port to open the local web server on
web-server-port: 8080
# Maximum time to keep spots and alerts in the system before deleting them. By default, one hour for spots and one week
# for alerts.
max-spot-age-sec: 3600
max-alert-age-sec: 604800
# Login for QRZ.com to look up information. Optional. You will need an "XML Subscriber" (paid) package to retrieve all
# the data for a callsign via their system.
qrz-username: ""
qrz-password: ""
# Login for HamQTH to look up information. Optional.
hamqth-username: ""
hamqth-password: ""
# API key for Clublog to look up information. Optional. You sill need to request one via their helpdesk portal if you
# want to use callsign lookups from Clublog.
clublog-api-key: ""
# Allow submitting spots to the Spothole API?
allow-spotting: true
# Options for the web UI.
web-ui-options:
spot-count: [10, 25, 50, 100]
spot-count-default: 50
max-spot-age: [5, 10, 30, 60]
max-spot-age-default: 30
alert-count: [25, 50, 100, 200, 500]
alert-count-default: 100