forked from cerc-io/stack-orchestrator
Prathamesh Musale
33d395e213
- The instructions to `Deploy Gitea Package Registry` from build-support [readme](https://git.vdb.to/deep-stack/stack-orchestrator/src/branch/pm-update-registry-steps/stack_orchestrator/data/stacks/build-support#2-deploy-gitea-package-registry) don't seem to be in a working state - Updated `package-registry` stack instructions to use deployment pattern Reviewed-on: cerc-io/stack-orchestrator#937 Reviewed-by: ashwin <ashwin@noreply.git.vdb.to> Reviewed-by: David Boreham <dboreham@noreply.git.vdb.to> Co-authored-by: Prathamesh Musale <prathamesh.musale0@gmail.com> Co-committed-by: Prathamesh Musale <prathamesh.musale0@gmail.com> |
||
|---|---|---|
| .. | ||
| README.md | ||
| stack.yml | ||
Package Registry Stack
The Package Registry Stack supports a build environment that requires a package registry (initially for NPM packages only).
Setup
-
Setup required repos and build containers:
laconic-so --stack package-registry setup-repositories laconic-so --stack package-registry build-containers -
Create a deployment:
laconic-so --stack package-registry deploy init --output package-registry-spec.yml # Update port mapping in the laconic-loaded.spec file to resolve port conflicts on host if any laconic-so --stack package-registry deploy create --deployment-dir package-registry-deployment --spec-file package-registry-spec.yml -
Start the deployment:
laconic-so deployment --dir package-registry-deployment start -
The local gitea registry can now be accessed at http://localhost:3000 (the username and password can be taken from the deployment logs)