Package
ci / checks (push) Successful in 48m34s

This commit is contained in:
khodowany
2026-09-30 19:46:37 -05:00
parent 2a1aa2c67a
commit 09656a9d60
6621 changed files with 698 additions and 774 deletions
+6 -4
View File
@@ -13,10 +13,12 @@ python3 modulus.py package
Copy the tarball to the Zero, verify its `.sha256`, unpack it anywhere, and run:
```sh
sudo zero/install-zero.sh
sudo zero/install_zero.sh
```
The installer loads `zero/product-vamp-zero-linux-arm64.docker.tar`, installs `/etc/product-vamp/vamp.json` if missing, configures NetworkManager AP mode, and enables the systemd units.
The installer loads `zero/product_vamp_zero_linux_arm64.docker.tar`, installs `/etc/product_vamp/vamp.json` if missing, configures NetworkManager AP mode, and enables the systemd units.
Project-owned install paths, services, executables, and archives use underscores. The checkout and Git URL remain `product-vamp`. On upgrades, the installer validates and probes the incoming image before removing the old hyphenated Product Vamp paths, services, and network profile. Unrelated services, networks, and data are preserved; symlinked installation paths are rejected.
On reinstalls, the installer skips apt entirely when the required OS packages are already present. If packages are missing, the Zero needs upstream internet before the installer can finish provisioning Docker, NetworkManager, and SQLite.
@@ -29,7 +31,7 @@ Defaults:
- Zero IP: `192.168.42.1`
- API: `http://192.168.42.1:8080`
For API-only quick checks, set `runtime.headless` to `true` or run `vamp-zero --once` from a development build.
For API-only quick checks, set `runtime.headless` to `true` or run `vamp_zero --once` from a development build.
Score inputs are tracked under `data/songs/`. The build/package step generates acoustic, electric, and vocal parts, engraved pages, audio, and the read-only catalog database. Installation replaces these assets together; no database migration or runtime score import is needed.
@@ -38,7 +40,7 @@ Score inputs are tracked under `data/songs/`. The build/package step generates a
Hold BOOTSEL while plugging the Pico into USB, then copy:
```text
pico/product-vamp-pico2w.uf2
pico/product_vamp_pico2w.uf2
```
to the mounted `RPI-RP2` drive.