app-privategit-design

PointSav PrivateGit Design

Self-hosted design-system engine — token gallery, component docs, Writing/Paper content, and an on-prem MCP endpoint, running on your own infrastructure

BETA · freeFSL-1.1-ALv2Deliveryv0.1.0

Turns a machine into your organisation's design system.

Platform

PlatformDownload
aarch64 (seL4/Microkit appliance)aarch64-unknown-linux-gnu

Boot

curl -fsSL https://software.pointsav.com/releases/app-privategit-design/0.1.0/aarch64-unknown-linux-gnu -o aarch64-unknown-linux-gnu
This ships as a bootable seL4/Microkit/libvmm appliance image (loader.img), not
a regular Linux binary — boot it under QEMU rather than running it directly.

Real qemu invocation (adapt paths to wherever you place the downloaded image):

  qemu-system-aarch64 \
    -machine virt,virtualization=on,secure=off \
    -cpu cortex-a53 \
    -serial mon:stdio \
    -device loader,file=./aarch64-unknown-linux-gnu,addr=0x70000000,cpu-num=0 \
    -m size=2G \
    -nographic \
    -global virtio-mmio.force-legacy=false \
    -drive file=./blk_storage,format=raw,if=none,id=hd \
    -device virtio-blk-device,drive=hd,bus=virtio-mmio-bus.1 \
    -device virtio-net-device,netdev=netdev0,bus=virtio-mmio-bus.0 \
    -netdev user,id=netdev0,hostfwd=tcp::9094-:9094

This runs under TCG software emulation (no KVM/hardware-virt required — works
on any host, including non-aarch64 hosts, but slower than native).

Before first boot, create the data disk file referenced above — QEMU will not
start without it:

  qemu-img create -f raw blk_storage 2G

The guest formats this disk to ext4 itself automatically on first boot if it's
blank, then mounts it directly on every later boot — your data genuinely
persists across restarts as long as you keep reusing the same blk_storage file.

Once booted, the design engine is reachable at http://127.0.0.1:9094 on the
host (forwarded from the guest).

Known limitation: there is no supported host-side graceful shutdown for this
image today — stopping the VM (Ctrl-C, kill, or equivalent) hard-kills the
emulator process; there is no in-guest ACPI/power-button path to receive a
shutdown request from the host side. Avoid stopping the VM while writes are
actively in flight if you can avoid it.

Version & checksum

v0.1.0

SHA256: verifying… — verify via MANIFEST

← All products