stack-orchestrator/stack_orchestrator/data/stacks/package-registry
Prathamesh Musale 33d395e213
All checks were successful
Lint Checks / Run linter (push) Successful in 36s
Publish / Build and publish (push) Successful in 1m9s
Smoke Test / Run basic test suite (push) Successful in 4m0s
Webapp Test / Run webapp test suite (push) Successful in 4m33s
Deploy Test / Run deploy test suite (push) Successful in 4m55s
Fixturenet-Laconicd-Test / Run Laconicd fixturenet and Laconic CLI tests (push) Successful in 13m59s
K8s Deploy Test / Run deploy test suite on kind/k8s (push) Successful in 7m42s
Database Test / Run database hosting test on kind/k8s (push) Successful in 9m52s
Container Registry Test / Run contaier registry hosting test on kind/k8s (push) Successful in 3m37s
External Stack Test / Run external stack test suite (push) Successful in 4m46s
Add package registry stack instructions (#937)
- 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: #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>
2024-08-23 09:42:44 +00:00
..
README.md Add package registry stack instructions (#937) 2024-08-23 09:42:44 +00:00
stack.yml Update independent act-runner stack to use custom act as well. (#702) 2024-01-15 12:10:48 -06:00

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)