shoelaces/test/integ-test/expected-results, branch master

Update example templates to modern distros

2026-06-06T00:19:48+00:00

Replace CoreOS (EOL) with Flatcar Linux using Ignition v3. Replace CentOS (EOL) with AlmaLinux using a kickstart template. Update Ubuntu templates to jammy with current archive mirror paths. Update Debian template to bookworm. Drop CoreOS cloud-config; add Flatcar Ignition example. Update mappings.yaml, test configs, fixtures, and smoke test accordingly.

Remove Bootstrap, Glyphicon fonts, and unused CSS

2026-06-05T20:54:14+00:00

Drops bootstrap.css, bootstrap.min.css, default.css (now folded into main.css), and the full glyphicons font set (~538KB total).

test: add frontend smoke js test

2026-06-04T19:54:47+00:00

Style: How client and server interact during poll

2023-01-23T18:21:36+00:00

The iPXE client just repeats the same request, a.k.a. "polling". It is the Shoelaces server that can break the polling loop. Either by handing out automated boot entry point based on IP address or DNS PTR record, hand picked boot entry point from Web UI or due retry maximum reached. Signed-off-by: Geert Stappers

test: add test for /start endpoint (#23)

2023-01-09T18:29:18+00:00

In commit 1c79728984af was endpoint '/start' added, now it is tested. Signed-off-by: Geert Stappers

style: add clarifying comments in polling iPXE scripts

2023-01-09T18:18:40+00:00

* String changes in internal/polling/polling.go The most important one, from the point of view of human user, is the addition of telling that a maximum retry has been reached. The poll script got rid of the way too long line. That is done by using "iPXE script continueing line character", \, backslash. Poll interval shorter, from ten seconds to seven seconds, also from 10000 ms to more readable 7000 ms (clearly three zeros (how many zeros are in 10000? (four or five?))). Added information about a loop that only looks like a loop. A minor `s/iPXE/iPXE client/`. In directory test/integ-test/expected-results/ are poll-unknown.txt and poll.txt updated for getting a clean `make test`. * style: build on top of latest contribution In particular, mentioning 'maxRetry' exposes implementation code to the end user, which we should avoid. Co-authored-by: Raul Benencia

test: fix test for behavior modified in 3233a856

2023-01-04T20:22:43+00:00

Signed-off-by: Raul Benencia

First public commit

2018-05-11T22:02:34+00:00