Files
vpsmgr/docs/development.md
T
bluebluesoda 1b564a9900 feat(install): use container-only incus-base instead of full incus
- new installs pull incus-base (Zabbly lts-7.0) which ships the same
  incusd daemon without the QEMU/SPICE/Ceph VM stack (~240 MiB less
  download, 500 MiB+ less disk)
- leave hosts that already carry the full `incus` package untouched
- uninstall --purge now also removes the full-incus VM dependencies,
  guarded by an installed reverse-dependency check (never blanket autoremove)
- update the dev docs install snippet to incus-base

Generated with Codebuff 🤖
Co-Authored-By: Codebuff <noreply@codebuff.com>
2026-08-30 08:19:19 +00:00

74 lines
2.7 KiB
Markdown

# Development
## Building
`./build.sh [VERSION]` compiles the Go binary into `bin/vps`. It requires
any Go that supports toolchain auto-switch (≥ 1.21); `src/go.mod` pins the
exact toolchain (go1.26.5).
```sh
./build.sh # current OS/arch
GOOS=linux GOARCH=arm64 ./build.sh # cross-compile
```
**Always `CGO_ENABLED=0`** (build.sh and the release workflow do this). The
project is pure Go with no cgo; leaving cgo on pulls in Go's `runtime/cgo`
bootstrap and a C toolchain whenever the standard `net` package is built,
which fails on machines with a broken/absent gcc. Release binaries are
therefore static and toolchain-free.
## Testing
```sh
cd src
CGO_ENABLED=0 go vet ./...
CGO_ENABLED=0 go test ./...
```
The CI release workflow also runs vet+test with `CGO_ENABLED=0` on amd64.
### Developing against Incus
The panel talks to Incus over its Unix socket (`/var/lib/incus/unix.socket`,
group `incus-admin`). For a local dev loop:
```sh
# add the Zabbly LTS repo and install Incus (Debian 12/13, Ubuntu 22.04+)
curl -fsSL https://pkgs.zabbly.com/key.asc -o /etc/apt/keyrings/zabbly.asc
echo 'deb [signed-by=/etc/apt/keyrings/zabbly.asc] https://pkgs.zabbly.com/incus/lts-7.0/ trixie main' > /etc/apt/sources.list.d/zabbly-incus.list
apt-get update && apt-get install -y incus-base # container-only build (no VM stack);
# install the full `incus` package only if you also develop against VMs
incus admin init --preseed < ... # or use scripts/10-incus.sh
usermod -aG incus-admin "$USER" # socket access without root
```
`vps install` does all of this on a real host; the exec API is exercised by
`internal/lx` over websockets (no `incus` CLI needed at runtime).
## Releasing
Tag a version (`v*`); the `.github/workflows/release.yml` builds amd64/arm64
with `CGO_ENABLED=0`, runs vet+test, attests build provenance (SLSA) and
uploads a release with checksums. `install.sh` downloads the prebuilt binary
from the latest release, falling back to a local build.
## Conventions
- Small, single-purpose commits — one commit per bug/feature.
- Commit messages follow the existing style (short subject, then a bullet
list of what and why).
- Shell scripts: `set -uo pipefail`, helpers `log`/`die`/`warn`, bash `-n`
checked, Python one-liners used only where the stdlib is enough.
- The panel templates embed two languages (`zh` / `en`) via `{{if eq .Lang
"zh"}}...{{else}}...{{end}}`.
## Repository layout
```
install.sh / uninstall.sh / build.sh # lifecycle + local build
scripts/ 00-check 10-incus 20-network 30-traefik 40-panel 50-image 60-rhel 70-opensuse 80-debian-dev 90-arch
configs/ reference configs (traefik / systemd / sudoers)
docs/ this documentation
src/ Go source (single binary: CLI + panel)
```