havayolu

What’s new

Follow what arrived in each version. Use the links to try the pages added in that version right away.

  1. v0.4.0 Automatic, verified release pipeline

    Current version

    • Every approved change will go live on its own once the tests pass: the app is built, sent to the server, and the new version is checked to be actually running. If it is not, the release is marked failed and reported.
    • If something goes wrong, the previous version can be restored with a single command; data is kept.
    • The server setup guide is ready. havayolu.live goes live once the setup is done.

  2. v0.3.2 Safer sign-in, sturdier server, open source

    • Admin sign-in can no longer be locked by someone else's failed attempts: the attempt limit is kept per visitor. The server no longer shuts out other users when the status page gets heavy traffic.
    • The server keeps running through a brief cache outage and no longer starts before the database is ready on first setup.
    • The language switch now works in the admin panel.
    • The source code is public under the MIT License. The page source carries an ownership and license notice; the havayolu name and logo are outside the license, rights reserved.

  3. v0.3.1 Our new name is havayolu, at havayolu.live

    • The app is now called havayolu. The website will go live at havayolu.live, the admin panel at admin.havayolu.live, the server at api.havayolu.live and the analytics panel at analiz.havayolu.live.
    • Visitors to www.havayolu.live are redirected to havayolu.live automatically.

  4. v0.3.0 All services, admin panel and consent-based visit analytics

    • Every part of the app is ready: web, server (API), two background workers, the database and two caches. They are packaged to be set up on the server in one go, and the same setup was run and tested on a computer.
    • Admin panel: it opens on its own domain and is protected by admin sign-in. The Services screen shows the status, version, latency and memory use of each service, and the last signal from the background workers.
    • Our own analytics app (Siteni Analiz Et) is connected; its panel uses the same admin account.
    • Visit statistics are measured only if you consent. You can change your choice at any time with “Analytics preferences” at the bottom of the page.
    • Security: security headers, request limits and rate-limited admin sign-in. Session keys are never stored in plain form on the server.

  5. v0.2.0 First local test environment: Status and What’s new pages

    • The app now starts on your computer with a single command (pnpm dev), so you can see every change locally without waiting for a deploy.
    • Status page: app version, server (API) connection and roadmap progress on one screen.
    • What’s new page: what arrived in each version, with direct links to the pages you can try in that version.
    • One-click switch between Turkish and English. Your choice is remembered.
    • Light and dark themes follow your system setting automatically.
    • The project code is released under the MIT license. Flight data keeps its own license (ADSB.lol, ODbL).

    Try it: Status page →Try it: What’s new page →

  6. v0.1.0 Project set up and roadmap defined

    • Data sources chosen: live positions from ADSB.lol (free, commercial use allowed), airports and runways from OurAirports, airlines and estimated routes from VRS standing-data, weather from NOAA.
    • Every data source and its license was verified as of 2026-09-25. Sources that forbid commercial use, and the official Flightradar24 API, are excluded.
    • Release pipeline designed: code pushed to GitHub is tested automatically, then deployed through Dokploy.
    • Development split into 5 parts with milestones. First goals, in order: the live map, then the “my aircraft is 10 km from the station” and “landed” alerts reaching your phone, then the mobile app.
    • Known limitation stated up front: without our own ADS-B receiver, landings will often be reported as “probably landed (estimated time)”.