mix/selfpost
1
0
Fork 0
Code Issues Pull Requests Actions 21 Packages Projects Releases Wiki Activity

release: 2.9.1: log panes wrap on a phone
test / test (push) Waiting to run
Details

Browse Source 
Cut without asking, as the owner said on 2026-10-15, for his report of
2026-10-16 (two scroll bars over a message's Delivery log on his phone).

Log panes wrap their lines under their start instead of scrolling
sideways (216f366 design, bd21ff0 code): the Delivery log of a message,
System log, the queue's listing. go vet, go test (26 packages) and make
e2e passed on the test server for that tree. No migration, schema 11.
The inbound-upstream-result mockup and plan (5348330, 295d72e) ride
along; its code follows for 2.10.0.

CHANGELOG [2.9.1]; pins in deploy/docker-compose.yml, README and the
guide (pin, build, the sample restore message); development's "from pin"
and row 31. No tag.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
mix
2026-10-16 14:31:58 +03:00
co-authored by Claude Opus 5.5
parent bd21ff0f90
commit 6531db977e
5 changed files with 14 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/guide.md
+4 -4
View File
@@ -204,14 +204,14 @@ cat ./data/setup-token
#### Fixed image tag
`deploy/docker-compose.yml` pins an explicit version (`ghcr.io/mixeme/selfpost:X.Y.Z`),
deliberately never `:latest`. The current pin is `2.9.0`. **No 2.x image is
deliberately never `:latest`. The current pin is `2.9.1`. **No 2.x image is
published on ghcr.io yet** (the newest there is `1.3.0`); until one is, build
it from the checkout under the pinned name, and Compose uses the local image
instead of pulling:
```sh
docker build -f build/Dockerfile --build-arg VERSION=2.9.0 \
-t ghcr.io/mixeme/selfpost:2.9.0 .
docker build -f build/Dockerfile --build-arg VERSION=2.9.1 \
-t ghcr.io/mixeme/selfpost:2.9.1 .
```
`VERSION` must equal the tag: it is the version the backup check compares
@@ -944,7 +944,7 @@ A version mismatch at step 5 refuses to start and leaves `/data` untouched —
the panel exits with a message naming the tag to use, e.g.:
```
backup: this backup was created by SelfPost 2.8.0 but this image is 2.9.0 — restore into the matching image (selfpost:2.8.0)
backup: this backup was created by SelfPost 2.9.0 but this image is 2.9.1 — restore into the matching image (selfpost:2.9.0)
```
Fix the tag in `docker-compose.yml` (build that tag as under [Fixed image