Skip to content

obc data v2 · P3 — The local target and obc data serve #2651

Closed

Description

@timohueser

Part of #2648. Read the epic first: it holds the model and the decisions.

Goal

A developer bakes a small area into local and opens every app against it with one command. One program serves any target: obc data serve serves local here, and in P4 the VPS runs the same program for prod.

Scope

  1. obc data serve [TARGET] (default local). It runs the routing service (planner/service), the search service, the downloads service and a static file server over the target's files, on fixed ports. It prints the links: web planner, map builder, desktop app, simulator, and the iPhone URL on this Wi-Fi.

  2. Serve follows its target. When local's release.json changes, it loads the new release beside the current one, then switches. Build this as the code that P4 extends with HTTPS polling, next.json and ready. Do not write a second follower.

  3. Apps accept another catalog. Today the URLs are fixed:

    • web planner: PLANNER_CATALOG in builder/web/src/lib/planner/release.ts;
    • map builder and desktop app: DEFAULT_CATALOG_URL in builder/desktop/src/catalog.rs;
    • iOS: PlannerService(catalogURL:).

    Add one override per app (a query parameter or an environment variable) that serve sets or prints. The simulator loads the map from local.

  4. Delete:

    • obc data dev (cli/dev_cli.rs, dev.rs, dev/);
    • the portable-provenance adoption (local.rs);
    • obc planner serve and tools/planner_local.py.

Acceptance

  • On a clean laptop:
    • obc data update local --region freiburg, then obc data serve;
    • the web planner routes and searches;
    • the map builder lists the local catalog and assembles a map;
    • the simulator loads that map.
  • A second update local with --only device/map switches serve to the new release without a restart.
  • Focused tests for the follow logic on a dir target. Run the suites of each crate and app you change. Report added and removed lines.

Depends on

P2.

Activity

  1. timohueser commented on Oct 12, 2026

    @timohueser
    OwnerAuthor

    P3 code is merged in two pull requests:

    • obc data v2 · P3-a — obc data serve follows a dir target #2669: obc data serve [TARGET]. It serves a dir target on port 8710 on every IPv4 address. It follows release.json, and it starts the planner services of a new release beside the current ones. Clients change to the new release when its services answer. A rollback changes back at once. When a ready service stops, its release fails and its API answers 404. SIGINT, SIGTERM and SIGHUP stop it. On Linux, the child services stop when serve dies. Plain http:// is accepted only at an IP address. New: tiles_origin in data/planner-runtime.toml.
    • obc data v2 · P3-b — the apps read the catalogue of obc data serve #2671: the web planner reads VITE_PLANNER_CATALOG. The iOS Debug build reads -OBCPlannerCatalog and accepts the scheme of the catalogue for its release URLs. Root-relative config resolution is removed. companion-ios/README.md has a "Local planner data" section.

    This issue stays open for the checks that CI cannot do:

    • the clean-laptop acceptance: obc data update local, obc data serve, then the web planner and a phone against it;
    • the map-builder assembly and the simulator;
    • on an iPhone: the Local Network alert appears (no NSLocalNetworkUsageDescription), and ATS permits plain http to the laptop's IP address.

    The follow-up for P4 (#2652) is recorded there: serve needs a /planner-offline/ route, and iOS takes the offline API from the catalogue origin.


    Generated by Claude Code

  2. timohueser commented on Nov 4, 2026

    @timohueser
    OwnerAuthor

    This issue is closed because the work is done. The code merged in #2669 and #2671 (VITE_PLANNER_CATALOG, -OBCPlannerCatalog). obc data serve runs in prod as the follower (#2841) and locally every day. The one open check, iPhone Local Network and ATS against a local serve, moves to #1978.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestinfraTooling, scaffold, CI, dev harness

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions