Added
FORCE_SCRIPT_NAME/ sub-path mount support for the in-browser HTTP API client (v0.7.1, #987, closes Action Tracker #123) — new template tag{% djust_client_config %}indjust.templatetags.live_tagsemits<meta name="djust-api-prefix" content="...">. The content is derived via Django'sreverse()so it honors bothFORCE_SCRIPT_NAMEand any customapi_patterns(prefix=...)mount. The djust client reads this meta tag once at bootstrap (00-namespace.js) and exposes two helpers:window.djust.apiPrefix(resolved prefix string) andwindow.djust.apiUrl(path)(prefix + path joiner with slash normalization).djust.call()(48-server-functions.js) now routes throughdjust.apiUrl()— the last remaining hardcoded/djust/api/reference in the client bundle is gone. Priority: explicitwindow.djust.apiPrefix> meta tag > compile-time default/djust/api/. Integrators mounting djust behind a reverse proxy prefix now only need to add{% load live_tags %}{% djust_client_config %}to their base template<head>; no JS patching required. Covered by 12 new tests (5 Python intest_client_config_tag.py, 6 JS inapi_prefix.test.js, 1 regression inserver_functions.test.jsassertingdjust.callhonors the meta tag under a forced script prefix). Bundle size delta: +148 B gzipped (50030 → 50178 B). Docs: "Sub-path deploys" section added todocs/website/guides/server-functions.mdanddocs/website/guides/http-api.md. Follow-up issue #992 filed for the same class of bug in03b-sse.js:44(SSE fallback transport, v0.7.2 target).