Settings — Flight Tracker

260 days until the Glasgow deadline (2027-04-25)

Travelpayouts token not configured. No price data can be collected yet. Add TRAVELPAYOUTS_TOKEN to /opt/flighttracker/.env and run flighttracker restart. The first scan starts within a minute of the token appearing.

← Dashboard

Search settings

saved to /data/settings.json — no rebuild needed

Trip

Hard deadline (be in Glasgow by) Search window start Search window end

Stay length min (days) Stay length max (days)

The outbound leg is searched up to the hard deadline; the inbound leg trails it by the stay length, so inbound dates are searched past the deadline automatically.

Airports

Outbound origins Outbound destinations

Inbound origins (UK exit) Inbound destinations (home)

Space- or comma-separated 3-letter IATA codes. Every origin/destination combination becomes one API call per month of the search window, so adding airports multiplies the scan cost.

Scan

Candidates kept per scan Daily run hour (0–23, local) Daily run minute

Current settings produce about 87 Travelpayouts calls per scan. The free tier allows 300 requests per minute, so this is well within limits.

Alerts

Drop threshold (%) Baseline undercut (%) Baseline window (days) Repeat cool-off (days)

To force a test alert, set the drop threshold to 1 and run a scan twice, then set it back.

Credentials

read from .env, not editable here

Travelpayouts token

missing

Brevo SMTP email

missing — alerts still recorded, just not emailed

Edit /opt/flighttracker/.env then run flighttracker restart. Any $ in a value must be written as $$ — Docker Compose interpolates env_file values.