Installer: support Forgejo as catalog source; NPM dashboard bound to internal IP
Co-Authored-By: Claude Code <noreply@anthropic.com>
This commit is contained in:
parent
d66db4e85e
commit
3c994af96b
4 changed files with 27 additions and 4 deletions
11
README.md
11
README.md
|
|
@ -159,6 +159,17 @@ installer authenticates its API and raw requests automatically: `HOMELAB_GITHUB_
|
|||
`GITHUB_TOKEN` / `HOMELAB_TOKEN`). The repository must be pushed — the installer reads from GitHub,
|
||||
not from your local checkout.
|
||||
|
||||
**Forgejo (self-hosted)**: set `HOMELAB_API_BASE` and `HOMELAB_RAW_BASE` (any value other than the
|
||||
GitHub defaults switches the installer to Forgejo URL/API patterns). Example — the homelab's own
|
||||
Forgejo at `http://10.0.0.5:3000` (repo `Homelab/repo`, branch `master`):
|
||||
|
||||
```bash
|
||||
export HOMELAB_OWNER=Homelab HOMELAB_REPO=repo HOMELAB_BRANCH=master
|
||||
export HOMELAB_API_BASE=http://10.0.0.5:3000/api/v1
|
||||
export HOMELAB_RAW_BASE=http://10.0.0.5:3000
|
||||
bun run src/index.ts list
|
||||
```
|
||||
|
||||
Adding a new service means adding a folder plus its `metadata.json` and regenerating the catalog:
|
||||
|
||||
```bash
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue