docs(registry-assuming): 📝 Update registry URLs and usage examples in documentation files

Co-Authored-By: Lilith Autocommit <noreply@atlilith.com>
This commit is contained in:
autocommit 2026-06-10 21:09:24 -07:00
parent 584120d97a
commit 52dccde071
3 changed files with 12 additions and 12 deletions

View file

@ -325,7 +325,7 @@ npm publish --no-git-checks --registry <url>
**Registry URL**:
- Environment: `LOCAL_PUBLISH_NPM_REGISTRY`
- Default: `http://npm.black.local/`
- Default: `http://npm.black.lan/`
- Override: `--registry` flag
**Auth Token**:
@ -349,7 +349,7 @@ twine upload dist/* --repository-url <url>
**Registry URL**:
- Environment: `LOCAL_PUBLISH_PYPI_REGISTRY`
- Default: `http://forge.black.local/api/packages/lilith/pypi`
- Default: `http://forge.black.lan/api/packages/lilith/pypi`
- Override: `--registry` flag
**Auth Token**:
@ -436,8 +436,8 @@ When `--dry-run` flag is provided:
| Variable | Used By | Default | Purpose |
|----------|---------|---------|---------|
| `LOCAL_PUBLISH_NPM_REGISTRY` | TypeScript | `http://npm.black.local/` | npm registry URL |
| `LOCAL_PUBLISH_PYPI_REGISTRY` | Python | `http://forge.black.local/api/packages/lilith/pypi` | PyPI registry URL |
| `LOCAL_PUBLISH_NPM_REGISTRY` | TypeScript | `http://npm.black.lan/` | npm registry URL |
| `LOCAL_PUBLISH_PYPI_REGISTRY` | Python | `http://forge.black.lan/api/packages/lilith/pypi` | PyPI registry URL |
---

View file

@ -93,7 +93,7 @@ npx @lilith/dev-publish --verbose
**Publish Failed**
```bash
# Check registry connectivity
curl -I http://npm.black.local/
curl -I http://npm.black.lan/
# Verify token is valid
echo $FORGEJO_NPM_TOKEN
@ -105,7 +105,7 @@ echo $FORGEJO_NPM_TOKEN
- `FORGEJO_NPM_TOKEN` - npm registry authentication token
**Optional:**
- `LOCAL_PUBLISH_NPM_REGISTRY` - Registry URL (default: `http://npm.black.local/`)
- `LOCAL_PUBLISH_NPM_REGISTRY` - Registry URL (default: `http://npm.black.lan/`)
## Exit Codes

View file

@ -2,7 +2,7 @@
Fast local build+publish utility for the `@packages` workspace. Publishes TypeScript packages with dev versions directly to local Verdaccio (`localhost:4874`), bypassing Forgejo CI/CD delays during co-development.
> **Note**: The default registry is now `localhost:4874` (local Verdaccio). Use `--remote` to explicitly publish to `npm.black.local` (requires Verdaccio authentication, not Forgejo token).
> **Note**: The default registry is now `localhost:4874` (local Verdaccio). Use `--remote` to explicitly publish to `npm.black.lan` (requires Verdaccio authentication, not Forgejo token).
## Installation
@ -36,7 +36,7 @@ Options:
-v, --verbose Detailed logging
--registry <url> Override registry URL
--local Publish to local Verdaccio (localhost:4874) - default
--remote Publish to remote Verdaccio (npm.black.local) - requires Verdaccio auth
--remote Publish to remote Verdaccio (npm.black.lan) - requires Verdaccio auth
--skip-version-check Don't check if version already exists
-h, --help Show help
--version Show version
@ -121,7 +121,7 @@ dev-publish supports `.env` file configuration for persistent settings. Configur
# Registry URLs
DEV_PUBLISH_REGISTRY=http://localhost:4874/
DEV_PUBLISH_REMOTE_REGISTRY=http://npm.black.local/
DEV_PUBLISH_REMOTE_REGISTRY=http://npm.black.lan/
# Authentication (only needed for --remote)
DEV_PUBLISH_AUTH_TOKEN=your-verdaccio-token
@ -139,7 +139,7 @@ DEV_PUBLISH_REMOTE=false
| Variable | Description | Default |
|----------|-------------|---------|
| `DEV_PUBLISH_REGISTRY` | Default registry URL | `http://localhost:4874/` |
| `DEV_PUBLISH_REMOTE_REGISTRY` | Remote registry URL (for `--remote`) | `http://npm.black.local/` |
| `DEV_PUBLISH_REMOTE_REGISTRY` | Remote registry URL (for `--remote`) | `http://npm.black.lan/` |
| `DEV_PUBLISH_AUTH_TOKEN` | Auth token for remote publishing | (none) |
| `DEV_PUBLISH_VERBOSE` | Enable verbose logging | `false` |
| `DEV_PUBLISH_SKIP_BUILD` | Skip build step | `false` |
@ -223,13 +223,13 @@ These are still supported for backwards compatibility:
Error: FORGEJO_NPM_TOKEN environment variable not set
```
This only occurs when using `--remote` to publish to `npm.black.local`.
This only occurs when using `--remote` to publish to `npm.black.lan`.
**Solution**: Either:
- Use local registry (default): `npx @lilith/dev-publish` (no auth needed)
- Set up Verdaccio authentication for remote publishing
> **Note**: The `FORGEJO_NPM_TOKEN` is a Forgejo access token and does NOT work with Verdaccio's htpasswd/JWT auth system. For remote Verdaccio publishing, you need to create a Verdaccio user with `npm adduser --registry http://npm.black.local/`.
> **Note**: The `FORGEJO_NPM_TOKEN` is a Forgejo access token and does NOT work with Verdaccio's htpasswd/JWT auth system. For remote Verdaccio publishing, you need to create a Verdaccio user with `npm adduser --registry http://npm.black.lan/`.
### Build Failed