From @NotRetarded's interface review, written on a phone while checking the previous release's mobile changes.
The action buttons are emoji now
🔎 check · 🔃 update · 📌 pin · 🛑 stop · 🔁 auto · ⚠️ major-confirm
The argument that decided it is one the project made against itself: the legend under the container table exists because the previous line-art set needed explaining. A 📌 does not need a legend.
The trade that comes with it is real — emoji render differently per platform and cannot be recoloured, so the table is louder than it was. One departure from the request: 🔊 was suggested for major-confirm, which reads as "sound". ⚠️ says what it means.
The filled button backgrounds are gone where a glyph carries its own state. They existed so a monochrome icon could signal "dangerous" or "on", and stacking the two fights: 🛑 on a red button is red on red, which reads worse than the white cross it replaced.
Half of every container's log was being thrown away
The report was that asking for 50 lines did not show 50. It did not reproduce as described — 50 gives 50, measured against a container with 500 lines. So I went looking for the case that would make the report right, and found something worse.
Every caller read logs as result.stdout or result.stderr. That takes stdout whenever it is non-empty and silently drops the other stream. On a container writing 30 lines to each:
docker logs 60 lines
Docksentry showed 30 lines — and the missing half was stderr
The error output. The half you open a log page to read. It also makes --tail 50 look like it returned fewer than 50, which is exactly how it surfaced.
Merged in backend.logs() rather than at the four call sites that shared the bug, so a fifth cannot get it wrong, and merged in the order the container wrote them rather than one stream after the other.
Smaller things from the same review
The logs page opens on Docksentry with 100 lines, instead of an empty frame and 50. When an update fails, that is the container you want, and fifteen containers already produce more than 50 lines of its own output.
The cron preview labels its first entry — "18:23 · today 21:23 · tomorrow" gave no way to tell which of the three had already happened.
Still on the list
The settings-page reorganisation (moving the cards that float below every tab into the tab each belongs to) is not in here. I attempted it twice and backed both attempts out — the second left a duplicated tab pane. It is a correct criticism and it will come, but not half-done.
Per-container memory and CPU on the status page is also still open: doing it properly means loading it after the page renders rather than making every page load wait two seconds for docker stats.
Upgrading is the usual docker pull ghcr.io/amayer1983/docksentry:latest, or nothing at all with auto-selfupdate on.