Skip to content

0.6.0: update with docker compose pull alone - #19

Merged
Ivamic merged 13 commits into
mainfrom
feat/pull-updates
Oct 26, 2026
Merged

Ivamic merged 13 commits into
mainfrom
feat/pull-updates

Conversation

@Ivamic

@Ivamic Ivamic commented Oct 26, 2026

Copy link
Copy Markdown
Owner

Work in progress towards 0.6.0. From this release on, updating is docker compose pull && docker compose up -d: no git pull, and compose.yaml and .env stay compatible within a major version.

Done so far:

  • compose.yaml pulls the images of the major version (tag 0) and reads the settings from .env (env_file); building from source moves to compose.build.yaml.
  • An empty value in .env means the default, except where it turns a feature off (geocoder, tag, automatic modules…).
  • Releases publish the major tag and attach compose.yaml and example.env, for installing without git.
  • CI checks compose.yaml with the required settings only and the update from the last release.
  • The core stops with a clear message on a database migrated by a newer version.
  • Core and worker accept each other within a range of protocol versions; refused or outdated workers show up on the Processing page.
  • Renamed settings keep their old names with a warning; unknown STEWARD_* names are logged.

Still to come: version in the UI and an update check, a heatmap of located photos on the map, copying coordinates, a gallery mark for photos with a located neighbor in time, documentation without git pull.

🤖 Generated with Claude Code

Ivamic and others added 13 commits October 26, 2026 10:52
… it wraps

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ajor version

compose.yaml pulls the images of the major version (tag 0) and reads the settings from .env
(env_file), so it stays the same within a major version; building from source moves to
compose.build.yaml. An empty value in .env means the default, except where it turns a feature
off. Releases publish the major tag and attach compose.yaml and example.env, for installing
without git. CI checks compose.yaml with the required settings only and the update from the last
release.

The core stops with a clear message on a database migrated by a newer version. Core and worker
accept each other within a range of protocol versions; a refused worker shows up on the
Processing page with the side to update, and a connected older one with the newer version.
Renamed settings keep their old names with a warning; unknown STEWARD_* names are logged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Twice a day the core asks GitHub for the latest release (not a pre-release); a newer one shows
up in the header with a link to its release notes, until closed. Settings has a new Updates
section with the version of the app, the switch of the check for the whole installation (on by
default), what is sent and a button to check now. Installation-wide settings get their own
table (migration 0022).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A photo without a location gets a clock badge when a photo with one was taken within 15 minutes
(STEWARD_TIME_NEIGHBORS_NEARBY_MINUTES): filled when by the same camera, the stronger hint,
outlined when by another one, such as a phone. It stands next to the GeoCLIP crosshair, and a
new filter chip shows only these photos. As for time neighbors, archived photos count, trashed
ones and scans do not.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A copy button in the coordinates field of the photo card and of "Set location", and next to the
location in the details. Browsers give the clipboard API only to secure pages, so over plain
http:// at a LAN address the old execCommand copy is used; if that is refused too, the text is
selected for Ctrl+C.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A switch over the map of the photo card and of "Set location" shows where the library already
has photos, as a violet heat map: when one knows there are many photos of a place, it helps to
find it on the map. Off by default and remembered in the browser; the bar over the map is now
always there. The core sends cells of about 100 m with their number of photos, compressed and
with an ETag, so that an unchanged library is not sent again.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…photo details on hover

- The camera and album filters are lists with a search field when long: typing keeps the names
  that contain it, whatever the case and the accents; arrows, Enter and Esc work.
- A long press on a tile shows the photo large over the gallery until let go; a short one opens
  the card as before. The preview is loaded only then, not while scrolling.
- Resting the mouse on a tile shows its file name, when it was taken, the camera and the size;
  it can be turned off in Settings, a first personal setting (migration 0023).
- The badges of a tile get 14 px icons, centered on whole pixels.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Installation downloads compose.yaml and example.env from the latest release; updating is
docker compose pull and up. New: coming from 0.5 or older, Portainer and Synology, building from
source with compose.build.yaml, the Docker worker on the tag of the major version. Every README
has a notice about the one manual step to 0.6, and the changelog the 0.6.0 entry.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts:
#	frontend/src/lib/gallery/FilterBar.svelte
#	frontend/src/routes/+page.svelte
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The notice about the step to 0.6 in every README now says why and how, with the commands with
and without the worker; the usage guide covers the search in the lists, the long press and the
details on hover.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Ivamic
Ivamic merged commit b725036 into main Oct 26, 2026
5 checks passed
@Ivamic
Ivamic deleted the feat/pull-updates branch October 26, 2026 20:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant