wrolpi/pi-gen
Roland 02eb8d70e4
Caddy install: run gpg --dearmor with --batch --yes.
If the caddy keyring file already exists (left by a prior partial
install), gpg prompts to overwrite via /dev/tty, which fails under the
tty-less wrolpi-upgrade.service ("cannot open '/dev/tty'") and aborts
the upgrade. --batch --yes overwrites silently, making the caddy
install idempotent in all four scripts that share this pattern.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-05 13:03:11 -06:00
..
stage2/04-wrolpi Caddy install: run gpg --dearmor with --batch --yes. 2026-07-05 13:03:11 -06:00
build.sh pi-gen: clear leftover BUILD_DIR at startup (robust to killed builds) 2026-05-31 18:06:31 -06:00
config.txt Updating pi-gen build to use bookworm-arm64 branch. 2026-02-11 17:38:04 -07:00
README.md Building pi and debian images using branch by default, allowing specifying branch with -b option. 2026-02-22 15:09:15 -07: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. Convert a map PBF file to your initial map DB dump:

    docker run --rm -v /home/user/district-of-columbia-230111.osm.pbf:/data/region.osm.pbf lrnselfreliance/osm-map-dumper > pi-gen/stage2/04-wrolpi/files/map-db-gis.dump
    

    The output is already compressed (PostgreSQL custom format with --compress 9).

    Verify the dump format is correct:

    file pi-gen/stage2/04-wrolpi/files/map-db-gis.dump
    # Should show: "PostgreSQL custom database dump"
    
  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.