lange-python 0.3.19

A bundeld set of tools, clients for the lange-suite of tools and more.

lange-python

Python helpers and clients for Lange services.

Distribution CLI

Publish a distribution artifact to the app services distribution system:

export LANGE_LABS_API_KEY="your-api-key"
lange distribution publish \
  --path ./dist/app.dmg \
  --version 1.2.3 \
  --distribution-name desktop-app \
  --os macos

Apply a macOS app update after downloading the published zip artifact:

from pathlib import Path

from lange.distribution import DistributionClient

client = DistributionClient(distribution_name="desktop-app", api_key="your-api-key")

latest = client.check_for_update("1.2.3")
if latest:
    version, artifact_path = client.download(current_version="1.2.3")
    print(version, artifact_path)
    update_metadata = client.update(
        current_version="1.2.3",
        installed_app_path=Path("/Applications/Desktop App.app"),
        relaunch=True,
    )
    print(update_metadata["version"])
    # The caller should now shut down so the detached helper can replace and relaunch the app.

The distribution client also exposes status and reload() for refresh-aware integrations:

client = DistributionClient(distribution_name="desktop-app", api_key="your-api-key")

latest_version = client.search_for_update("1.2.3")
print(client.status)  # connected
print(client.update_state["can_download"])

client.reload()  # repeats the last update check
client.reload(api_key=None)  # clears authentication and marks the client unauthenticated

Tunnel worker

from lange.tunnel import Tunnel

tunnel = Tunnel(
    host="wss://tunnel.lange-labs.com",
    api_key="your-bearer-token",
    target="http://localhost:3000",
)

tunnel.start()
# ...
tunnel.reload()  # restarts the connection flow with the current API key
tunnel.reload(api_key=None)  # clears authentication and leaves the client unauthenticated
tunnel.stop()

Tunnel clients also expose a status property with one of: "unauthenticated", "off", "pending", "connected", or "failed".

The worker connects to /api/v1/tunnels/worker, consumes the worker_connected welcome payload, forwards HTTP bodies as base64-encoded bytes, and supports websocket relay sessions through the same control socket.