# creator5-custom-firmware -- TEST configuration
#
#     cp test.env.example test.env
#
# Nothing in this file ever reaches a printer. It configures the replica --
# the printer's real rootfs under qemu-mipsel -- and nothing else. Build
# inputs and anything that ships live in config.env.

# ---- the replica image (REQUIRED) ------------------------------------------
# This is the replica. It carries the printer's rootfs, its real /usr/prog and
# /usr/data, AND the stock package already installed on top of them -- so the
# genuine klipper daemons, nginx, python3, checkEboard, moonraker and the
# printer's own OpenSSL 1.0.2d are all there, and package decryption is
# verified against the real implementation rather than a stand-in.
#
# There is no second way in. A local path used to exist -- `make rootfs`
# unsquashed rootfs.squashfs out of a stock package and a thin container
# mounted it, with PROG_DUMP pointing at the factory image for /usr/prog --
# and it cost ~60s of setup per test while needing the proprietary package on
# disk. The image needs neither, so it is the only source now.
#
# PINNED TO A VERSION, NOT :latest. This image is the entire substrate the
# brick-safety gates run on; a floating tag would let it change under a green
# suite, which is the same silent drift the sha256 pins in .github/workflows
# exist to prevent. Bump it deliberately when you rebuild.
#
# Built by tools/replica/build-printer-image.sh. It contains proprietary
# FlashForge firmware.
PRINTER_IMAGE="monstrofil/creator5-printer:1.9.7-1.2.9-20260810"

# Real partition sizes, as `df -h` reports them on the printer itself.
# Until these are set the replica's prog/data partitions are unbounded, so an
# install that runs the machine out of space would pass here and fail there.
PROG_MB=""
DATA_MB=""