manual set urls for external collection

This commit is contained in:
Mik-TF
2024-05-13 19:10:10 -04:00
parent a4efec1aa3
commit 280652166f
40 changed files with 79 additions and 80 deletions

View File

@@ -1,6 +1,6 @@
# Adding a new package
Binary packages are added via providing [a build script](../../bins/), then an automated workflow will build/publish an flist with this binary.
Binary packages are added via providing a build script, then an automated workflow will build/publish an flist with this binary.
For example, to add `rmb` binary, we need to provide a bash script with a `build_rmb` function:
@@ -43,7 +43,7 @@ build_rmb() {
Note that, you can just download a statically build binary instead of building it.
The other step is to add it to workflow to be built automatically, in [bins workflow](../../.github/workflows/bins.yaml), add your binary's job:
The other step is to add it to workflow to be built automatically, in bins workflow, add your binary's job:
```yaml
jobs:

View File

@@ -26,13 +26,13 @@ You should see the qemu console and boot logs, wait for awhile and you can [brow
To stop the machine you can do `Control + a` then `x`.
You can read more about setting up a qemu development environment and more network options [here](../../qemu/README.md).
You can read more about setting up a qemu development environment and more network options [here](qemu_readme.md).
## Accessing node
After booting up, the node should start downloading external packages, this would take some time depending on your internet connection.
See [how to ssh into it.](../../qemu/README.md#to-ssh-into-the-machine)
See [how to ssh into it.](qemu_readme.md#to-ssh-into-the-machine)
How to get the node IP?
Given the network script `dhcp-range`, it usually would be one of `192.168.123.43`, `192.168.123.44` or `192.168.123.45`.

View File

@@ -21,7 +21,7 @@ While deploying on your local node, logs with `zinit log` would be helpful to se
## Using a test app
If you need to test a specific module or functionality, you can create a simple test app inside e.g. [tools directory](../../tools/).
If you need to test a specific module or functionality, you can create a simple test app inside e.g. tools directory.
Inside this simple test app, you can import any module or talk to another one using [zbus](../internals/internals.md#ipc).