From 187c06ef5a25e0d02527a94a802dd3213a4b417b Mon Sep 17 00:00:00 2001
From: David Boreham <david@bozemanpass.com>
Date: Thu, 23 Feb 2023 07:22:46 -0700
Subject: [PATCH] Add build stack doc

---
 app/data/stacks/build-support/README.md | 30 +++++++++++++++++++++++++
 app/data/version.txt                    |  2 +-
 2 files changed, 31 insertions(+), 1 deletion(-)

diff --git a/app/data/stacks/build-support/README.md b/app/data/stacks/build-support/README.md
index e69de29b..9f7a74b4 100644
--- a/app/data/stacks/build-support/README.md
+++ b/app/data/stacks/build-support/README.md
@@ -0,0 +1,30 @@
+# Build Support Stack
+
+## Instructions
+
+JS/TS/NPM builds need an npm registry to store intermediate package artifacts.
+This can be supplied by the user (e.g. using a hosted registry or even npmjs.com), or a local registry using gitea can be deployed by stack orchestrator.
+To use a user-supplied registry set these environment variables:
+
+`CERC_NPM_REGISTRY_URL` and 
+`CERC_NPM_AUTH_TOKEN`
+
+Leave `CERC_NPM_REGISTRY_URL` un-set to use the local gitea registry.
+
+### Build support containers
+```
+$ laconic-so --stack build-support build-containers
+```
+### Deploy Gitea Package Registry
+
+```
+$ laconic-so --stack package-registry setup-repositories
+$ laconic-so --stack package-registry deploy-system up
+This is your gitea access token: 84fe66a73698bf11edbdccd0a338236b7d1d5c45. Keep it safe and secure, it can not be fetched again from gitea.
+$ export CERC_NPM_AUTH_TOKEN=84fe66a73698bf11edbdccd0a338236b7d1d5c45
+```
+Now npm packages can be built:
+### Build npm Packages
+```
+$ laconic-so build-npms --include laconic-sdk
+```
diff --git a/app/data/version.txt b/app/data/version.txt
index 3a48763e..ebda7605 100644
--- a/app/data/version.txt
+++ b/app/data/version.txt
@@ -1,2 +1,2 @@
 # This file should be re-generated running: scripts/update-version-file.sh script
-v1.0.20-6c1bedc
+v1.0.21-c52f9e6