Final QA: clean install on a Raspberry Pi 4 (arm64) #6

New issue

Closed

opened 2026-07-07 16:51:32 +00:00 by claude-bot · 1 comment

claude-bot commented

2026-07-07 16:51:32 +00:00

Contributor

Goal

Verify the published arm64 image deploys cleanly on real hardware, per the M10 exit criterion ("a new user can follow the docs and have a working Iris in under 30 minutes").

Steps

Fresh Raspberry Pi 4, empty data/ directory
Follow the README 60-second quickstart using the published Forgejo-registry image
Configure location, WLED host, and segments
Confirm the app is healthy and the UI loads

Acceptance criteria

Clean deploy succeeds on arm64 with no manual patching
Setup completes in under 30 minutes following only the docs

Part of the M10 final QA pass (see roadmap history / CHANGELOG).

## Goal Verify the published arm64 image deploys cleanly on real hardware, per the M10 exit criterion ("a new user can follow the docs and have a working Iris in under 30 minutes"). ## Steps - [ ] Fresh Raspberry Pi 4, empty `data/` directory - [ ] Follow the README 60-second quickstart using the published Forgejo-registry image - [ ] Configure location, WLED host, and segments - [ ] Confirm the app is healthy and the UI loads ## Acceptance criteria - [ ] Clean deploy succeeds on arm64 with no manual patching - [ ] Setup completes in under 30 minutes following only the docs Part of the M10 final QA pass (see roadmap history / CHANGELOG).

claude-bot added the

labels

2026-07-07 16:53:27 +00:00

claude-bot added this to the v1.0.0 milestone

2026-07-15 15:33:03 +00:00

claude-bot referenced this issue

2026-08-31 02:04:37 +00:00

Drop arm64 / Raspberry Pi support: publish linux/amd64 only #79

claude-bot commented

2026-08-31 02:07:36 +00:00

Author

Contributor

Closing as obsolete — superseded by #79.

Iris no longer publishes an arm64 image, so there is no arm64 artifact to validate on a Pi. The rationale is recorded in #79 and in spec §13.4: arm64 was declared "a hard requirement" pre-implementation on the assumption that self-hosters would run Iris on a Raspberry Pi, but the repo and registry are private, no arm64 image has ever been run anywhere, and the emulated build was the largest single CI cost in the repo.

The underlying M10 exit criterion — "a new user can follow the docs and have a working Iris in under 30 minutes" — is not dropped. It stays covered by #7 (end-to-end operational dry run), which exercises the documented quickstart against real WLED hardware on the actual amd64 target. If a clean-install-from-docs check on a fresh amd64 host is wanted as its own gate, that is worth a separate issue rather than reusing this one.

Closing as obsolete — superseded by #79. Iris no longer publishes an arm64 image, so there is no arm64 artifact to validate on a Pi. The rationale is recorded in #79 and in spec §13.4: arm64 was declared "a hard requirement" pre-implementation on the assumption that self-hosters would run Iris on a Raspberry Pi, but the repo and registry are private, no arm64 image has ever been run anywhere, and the emulated build was the largest single CI cost in the repo. The underlying M10 exit criterion — *"a new user can follow the docs and have a working Iris in under 30 minutes"* — is **not** dropped. It stays covered by #7 (end-to-end operational dry run), which exercises the documented quickstart against real WLED hardware on the actual amd64 target. If a clean-install-from-docs check on a fresh amd64 host is wanted as its own gate, that is worth a separate issue rather than reusing this one.

claude-bot closed this issue

2026-08-31 02:07:38 +00:00

claude-bot referenced this issue

2026-08-31 02:08:01 +00:00

Drop arm64 / Raspberry Pi support: publish linux/amd64 only #79