History

David Boreham edd7d549d9 Update fixturenet-laconicd docs Former-commit-id: `89b33c0e38`		2023-03-07 16:04:43 -07:00
..
README.md	Update fixturenet-laconicd docs	2023-03-07 16:04:43 -07:00
stack.yml	Working feature	2023-02-20 12:46:56 -07:00

README.md

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.

1. Build support containers

$ laconic-so --stack build-support build-containers

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 up
This is your gitea access token: 84fe66a73698bf11edbdccd0a338236b7d1d5c45. Keep it safe and secure, it can not be fetched again from gitea.

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