From 33d395e2131a989d8b9f9c49fc619dc18d95da0f Mon Sep 17 00:00:00 2001 From: Prathamesh Musale Date: Fri, 23 Aug 2024 09:42:44 +0000 Subject: [PATCH] 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: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/937 Reviewed-by: ashwin Reviewed-by: David Boreham Co-authored-by: Prathamesh Musale Co-committed-by: Prathamesh Musale --- .../data/stacks/package-registry/README.md | 26 ++++++++++++++++++- 1 file changed, 25 insertions(+), 1 deletion(-) diff --git a/stack_orchestrator/data/stacks/package-registry/README.md b/stack_orchestrator/data/stacks/package-registry/README.md index ddb36a3f..98630804 100644 --- a/stack_orchestrator/data/stacks/package-registry/README.md +++ b/stack_orchestrator/data/stacks/package-registry/README.md @@ -2,4 +2,28 @@ The Package Registry Stack supports a build environment that requires a package registry (initially for NPM packages only). -Setup instructions can be found [here](../build-support/README.md). +## Setup + +* Setup required repos and build containers: + + ```bash + laconic-so --stack package-registry setup-repositories + laconic-so --stack package-registry build-containers + ``` + +* Create a deployment: + + ```bash + 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: + + ```bash + laconic-so deployment --dir package-registry-deployment start + ``` + +* The local gitea registry can now be accessed at (the username and password can be taken from the deployment logs)