MarlinFirmware + Klipper Docker handoff
Make the firmware build
reproducible before it runs.
Specify the firmware, board, source ref, and container image. Leave with two files: a Docker Compose build spec and a board-support request that has the details people need.
Trust boundary
A build handoff, not a pretend compiler.
This page generates files in your browser. It does not run Docker, compile MarlinFirmware or Klipper, reach an Unraid server, or submit a request to a community app store.
Inputs become two handoff artifacts
Read the explanation
Six inputs describe firmware, board, repository, ref, image and note. The generated download contains two artifacts: a Docker Compose string and a board-support request. Bars compare six input fields with two artifact entries at sixty pixels per count. Generation does not compile firmware, run Docker, deploy to Unraid or submit a request. The Compose service emits four environment entries: firmware, board identifier, source repository and source ref. The request record has nine fields including those inputs, schema version, timestamp and scope. Bars use forty pixels per field. Values are source-authored text, not validated build-system compatibility; mutable refs and example images do not guarantee reproducibility. The written command contains two shell operations joined by and: clone the repository branch, then echo a prepared-input message. It invokes zero compiler operations. Bars use one hundred pixels per operation. The script interpolates supplied strings; inspect the exported specification before executing it. Editing a draft does not change prior generated artifacts until Generate. Reset restores sample inputs and generates a new handoff.