|
All checks were successful
Lint Checks / Run linter (pull_request) Successful in 40s
Webapp Test / Run webapp test suite (pull_request) Successful in 5m3s
Smoke Test / Run basic test suite (pull_request) Successful in 4m39s
Deploy Test / Run deploy test suite (pull_request) Successful in 5m30s
K8s Deployment Control Test / Run deployment control suite on kind/k8s (pull_request) Successful in 7m28s
K8s Deploy Test / Run deploy test suite on kind/k8s (pull_request) Successful in 8m30s
|
||
|---|---|---|
| .. | ||
| 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)