docs(config): add GITEA_NPM_TOKEN to .env.example
Include Gitea npm registry variables (token, host, owner) so developers know which env vars to set for @bytelyst package access. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
parent
4f9ec3332f
commit
da98c9fd3f
@ -79,6 +79,13 @@ FIELD_ENCRYPT_KEY=
|
|||||||
# Product-specific MEK name in AKV — only for 'akv' provider
|
# Product-specific MEK name in AKV — only for 'akv' provider
|
||||||
FIELD_ENCRYPT_MEK_NAME=lysnr-mek
|
FIELD_ENCRYPT_MEK_NAME=lysnr-mek
|
||||||
|
|
||||||
|
# ── Gitea NPM Registry (private @bytelyst packages) ─────────
|
||||||
|
# Token for authenticating with the Gitea npm registry.
|
||||||
|
# Generate at: http://<GITEA_NPM_HOST>:3300/user/settings/applications
|
||||||
|
GITEA_NPM_TOKEN=
|
||||||
|
GITEA_NPM_HOST=localhost
|
||||||
|
GITEA_NPM_OWNER=learning_ai_user
|
||||||
|
|
||||||
# ── Product Identity ──────────────────────────────────────────
|
# ── Product Identity ──────────────────────────────────────────
|
||||||
DEFAULT_PRODUCT_ID=lysnrai
|
DEFAULT_PRODUCT_ID=lysnrai
|
||||||
|
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user