wrolpi/pi-gen
lrnselfreliance d69f8317aa
serve, single-file and readability-extractor install from a committed lockfile (#912)
They were installed with `npm i -g`, which pinned only the three top-level versions and
resolved their 156 dependencies fresh from the registry, so a forged TLS certificate (as
the eMudhra key compromise allowed) could change code WROLPi runs on every archive.
npm-tools/package-lock.json pins every package with its sha512, and install_npm_tools.sh
runs `npm ci` and links the commands into /usr/local/bin for every install path, upgrades,
both images and the archive container.  The app container's unpinned, unused global serve
is removed.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 10:39:08 -06:00
..
stage2/04-wrolpi serve, single-file and readability-extractor install from a committed lockfile (#912) 2026-10-31 10:39:08 -06:00
build.sh install.sh and both image builds run WROLPi only from a signed checkout (#909) 2026-10-30 21:27:41 -06:00
config.txt Debian 13 (trixie) rebase: docker, debian-live-config, and pi-gen builds. 2026-07-13 15:43:08 -06:00
README.md Remove stale Postgres references after SQLite cutover. 2026-07-18 13:28:54 -06:00

Pi-Gen

This directory exists to facilitate the creation of WROLPI Raspberry Pi OS images.

See https://github.com/RPI-Distro/pi-gen

Generate 64bit Raspberry Pi WROLPi image

  1. (Optional) Place any default map assets under pi-gen/stage2/04-wrolpi/files/ if the image should ship with preloaded map data. Maps use PMTiles files served from /media/wrolpi/map/.

  2. Run the build (or, with a specific git branch)

    • Build release branch (default)

      sudo ./build.sh
      
    • Build specific branch

      sudo ./build.sh -b master
      
  3. The images are now in the pi-gen directory.