paseo-webui

Builds a container image of the Paseo web UI (the app.paseo.sh client) so the whole Paseo stack can be self-hosted.

The image clones upstream getpaseo/paseo at the release recorded in .paseo-ref, runs the Expo web export (npm run build:web --workspace=@getpaseo/app), and serves the static dist/ with nginx (with SPA fallback for Expo Router deep links). The relay / daemon endpoint is entered at runtime in the UI, so the image behaves identically to app.paseo.sh.

Build

Forgejo Actions builds and pushes both latest and a release-specific tag such as paseo-v0.1.110 on:

• push to main touching Dockerfile, nginx.conf, .paseo-ref, or a workflow
• manual dispatch (optionally pinning a different upstream ref via paseo_ref)

The separate update-release.yml workflow runs nightly, finds the newest upstream release tag, including beta/prerelease tags, and commits an updated .paseo-ref when needed. That commit triggers the image build. The update helper refuses to move the tracked release backwards and promotes a prerelease to its stable counterpart when available. Set PASEO_CHANNEL=stable when running the helper to restrict it to stable releases.

Local build:

docker build --build-arg PASEO_REF="$(cat .paseo-ref)" -t paseo-webui:local .
docker run --rm -p 8080:80 paseo-webui:local   # http://localhost:8080

Rollback

Use an immutable release tag when a rollback is needed, including a beta tag, for example:

docker pull git.nimmog.uk/nimmo/paseo-webui:paseo-v0.1.100

Vega normally follows latest; the NixOS container is configured to pull that tag when activated. To keep Vega on an older release, temporarily change its image to the desired paseo-vX.Y.Z tag and deploy that NixOS revision. The nightly updater will continue tracking the newest release in .paseo-ref.

Deploy

Consumed by the paseo-webui oci-container on vega in the nixos-config repo, on the newt_default network and reached through Pangolin.