Category: Thread

  • 2025/08/21 [GADM-api]

    I moved handlers to dedicated package. I added publicly available token creation endpoint with 2 seconds rate limiter.

  • 2025/08/20 [GADM-api]

    I moved all database interactions to separate package. Each resource now has it’s own repository.

  • 2025/08/19 [GADM-api]

    Refactoring in progress. I am moving database calls to separate go-package.

  • 2025/08/18 [GADM-api]

    I deployed the docs pages! Additionally I purchased a domain. The API is now available under api.worldlines.dev.

  • 2025/08/17 [GADM-api]

    In a week, I’ll be leaving for a long holiday. Until then, I need to wrap up a few loose ends. I expect to finish a beta version of the GADM API before I go. Remaining tasks: Today, I started working on the documentation site. I’ll be using Hugo and GitHub Pages — a simple…

  • 2025/08/16 [GADM-api]

    The main goal of the refactoring has been achieved — all GADM endpoints now rely on the new Postgres tables. Along the way, I removed a significant amount of code tied to the old tables. The next step in improving the codebase will be to further separate database logic from the main package, making the…

  • 2025/08/15 [GADM-api]

    I continue working on leveraging adm and adm_geometries tables for all endpoints

  • 2025/08/14 [GADM-api]

    I’ve found, fixed and deployed fix to the reverse geocode sql query bug. I started refactoring the code – first step is to extract database “stuff” from main package. I will probably get inspired by repository patter from DDD. I started working on leveraging adm and adm_geometries tables for all existing endpoints. This is required…

  • 2025/08/11 [GADM-api]

    Reverse geocode endpoint is deployed to production 🙂

  • 2025/08/09 [GADM-api]

    I implemented the reverse geocode endpoint. Once I deploy new endpoint I will take some time to refactor the code. I need to better organize the packages and get rid of duplicated GADM data.