···59596060`apps/main-app` exposes domain claim/status XRPC endpoints:
61616262+- `place.wisp.v2.domain.claimSubdomain` (procedure / POST, wisp handles)
6263- `place.wisp.v2.domain.claim` (procedure / POST)
6464+- `place.wisp.v2.domain.delete` (procedure / POST)
6565+- `place.wisp.v2.domain.getList` (query / GET)
6366- `place.wisp.v2.domain.getStatus` (query / GET)
64676568The server validates **serviceAuth JWTs** (not cookie auth, not direct end-user access JWTs) on `/xrpc/*`.
···83868487### Local TLS Requirement (No Auto Cert Generation)
85888686-Some PDS proxy flows require HTTPS on `:443` for the proxied service endpoint.
8787-Cert generation is intentionally manual so SANs are explicit and correct for your environment.
8888-8989-Example with `mkcert`:
9090-9191-```bash
9292-mkcert -cert-file certs/dev-cert.pem -key-file certs/dev-key.pem regentsmacbookair localhost 100.64.0.2
9393-```
9494-9595-Use SANs that match exactly what your PDS will call (hostname and/or IP).
9696-`apps/main-app` can terminate TLS directly in local dev with:
9797-9898-```env
9999-PORT=443
100100-LOCAL_DEV_TLS=true
101101-LOCAL_TLS_CERT_PATH=./certs/dev-cert.pem
102102-LOCAL_TLS_KEY_PATH=./certs/dev-key.pem
103103-```
8989+`apps/main-app` now serves HTTP only. If you need HTTPS in local/proxy flows,
9090+terminate TLS in your reverse proxy or tunnel layer and forward plain HTTP to main-app.
104911059210693```bash
···11export * as PlaceWispV2DomainClaim from "./types/place/wisp/v2/domain/claim.js";
22+export * as PlaceWispV2DomainClaimSubdomain from "./types/place/wisp/v2/domain/claimSubdomain.js";
33+export * as PlaceWispV2DomainDelete from "./types/place/wisp/v2/domain/delete.js";
44+export * as PlaceWispV2DomainGetList from "./types/place/wisp/v2/domain/getList.js";
25export * as PlaceWispV2DomainGetStatus from "./types/place/wisp/v2/domain/getStatus.js";
36export * as PlaceWispV2Domains from "./types/place/wisp/v2/domains.js";