roysc/stack-orchestrator
1
0
Fork 0
Code Pull Requests Activity

Update fixturenet-laconicd docs

Browse Source 
Former-commit-id: 89b33c0e38383221d29955f240eabfc725d9d38a
This commit is contained in:
dboreham
2023-03-07 16:04:43 -07:00
parent 4092a127ef
commit edd7d549d9
3 changed files with 55 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
app/data/stacks/build-support/README.md
+9 -4
View File
@@ -11,20 +11,25 @@ To use a user-supplied registry set these environment variables:
Leave `CERC_NPM_REGISTRY_URL` un-set to use the local gitea registry.
### Build support containers
### 1. Build support containers
```
$ laconic-so --stack build-support build-containers
```
### Deploy Gitea Package Registry
Note that the scheme/gerbil builder container can take a while to build so if you aren't going to build scheme projects it can be skipped with:
```
$ laconic-so --stack build-support build-containers --exclude cerc/builder-gerbil
```
### 2. Deploy Gitea Package Registry
```
$ laconic-so --stack package-registry setup-repositories
$ laconic-so --stack package-registry deploy-system up
$ laconic-so --stack package-registry deploy 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
Ensure that `CERC_NPM_AUTH_TOKEN` is set with the token printed above when the package-registry stack was deployed (the actual token value will be different than shown in this example):
```
$ export CERC_NPM_AUTH_TOKEN=84fe66a73698bf11edbdccd0a338236b7d1d5c45
$ laconic-so build-npms --include laconic-sdk
```