Update registry deploy instructions
Former-commit-id: ea6f28a3deb8c09e56d0c68779fa5d212f869c33
This commit is contained in:
parent
6ee7c3bbba
commit
48a761875a
@ -24,8 +24,31 @@ $ laconic-so --stack build-support build-containers --exclude cerc/builder-gerbi
|
||||
```
|
||||
$ laconic-so --stack package-registry setup-repositories
|
||||
$ laconic-so --stack package-registry deploy up
|
||||
[+] Running 3/3
|
||||
⠿ Network laconic-aecc4a21d3a502b14522db97d427e850_gitea Created 0.0s
|
||||
⠿ Container laconic-aecc4a21d3a502b14522db97d427e850-db-1 Started 1.2s
|
||||
⠿ Container laconic-aecc4a21d3a502b14522db97d427e850-server-1 Started 1.9s
|
||||
New user 'gitea_admin' has been successfully created!
|
||||
This is your gitea access token: 84fe66a73698bf11edbdccd0a338236b7d1d5c45. Keep it safe and secure, it can not be fetched again from gitea.
|
||||
To use with laconic-so set this environment variable: export CERC_NPM_AUTH_TOKEN=3e493e77b3e83fe9e882f7e3a79dd4d5441c308b
|
||||
Created the organization cerc-io
|
||||
Gitea was configured to use host name: gitea.local, ensure that this resolves to localhost, e.g. with sudo vi /etc/hosts
|
||||
Success, gitea is properly initialized
|
||||
$
|
||||
```
|
||||
### 3. Configure the hostname gitea.local
|
||||
How to do this is OS-dependent but usually involves editing a `hosts` file. For example on Linux add this line to the file `/etc/hosts` (needs sudo):
|
||||
```
|
||||
127.0.0.1 gitea.local
|
||||
```
|
||||
Test with:
|
||||
```
|
||||
$ ping gitea.local
|
||||
PING gitea.local (127.0.0.1) 56(84) bytes of data.
|
||||
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.147 ms
|
||||
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.033 ms
|
||||
```
|
||||
|
||||
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):
|
||||
|
Loading…
Reference in New Issue
Block a user