Skip to content

armgit / laya

Public Imported from GitHub
0

Non-autoregressive System 1 decision engine. Typed choice, score and yes/no decisions over any text in a single forward pass, in 100+ languages, with a router that picks the right checkpoint per request.

fix(compose): forward the admission, budget and revision knobs to laya-serve

Aashish335cd3ce5deb
diff --git a/compose.http.yaml b/compose.http.yaml
index 0c7eeb39..30290504 100644
--- a/compose.http.yaml
+++ b/compose.http.yaml
@@ -50,7 +50,20 @@ services:
# Empty keeps Router's own default (2). Set 3 when LAYA_AUTO_TASK is on: that adds a
# third checkpoint routing can choose on demand, and a cap below it reloads one per switch.
LAYA_MAX_LOADED: "${LAYA_MAX_LOADED:-}"
+ # Requests admitted at once; one that arrives with every slot taken is refused with 503
+ # instead of queued, which is what bounds the bodies a burst holds in memory. Empty keeps
+ # the server's own default (16), so this line changes nothing until it is set.
+ LAYA_MAX_CONCURRENT: "${LAYA_MAX_CONCURRENT:-}"
+ # Ceiling on the `max_len` / `head_max_len` a request may ask for; a larger value comes back
+ # as 422. The SDK integrations quote 8192 because that is this service's default, so the
+ # default here stays empty: an operator who sets nothing gets the number the docs print.
+ LAYA_MAX_TOKEN_BUDGET: "${LAYA_MAX_TOKEN_BUDGET:-}"
LAYA_LOG_LEVEL: "${LAYA_LOG_LEVEL:-info}"
+ # The supply-chain pair: LAYA_REVISION says which Hub commit a checkpoint may load from (a
+ # commit, branch, tag, or `reviewed` for the SHAs in laya/revisions.py) and
+ # LAYA_SHA256_DIGESTS verifies the artifact that arrives. An empty revision is "not asked
+ # for", so unlike a name the server resolves, nothing is validated at startup here.
+ LAYA_REVISION: "${LAYA_REVISION:-}"
LAYA_SHA256_DIGESTS: "${LAYA_SHA256_DIGESTS:-}"
LAYA_API_KEY: "${LAYA_API_KEY:-}"
LAYA_API_KEY_FILE: "${LAYA_API_KEY_FILE:-}"