Install rclone and restic as the Docker image does and route /storage/restic/ and /storage/sync/ to rclone's restic and WebDAV servers. Updates add both to existing containers and restart Portabase, which looks for rclone only at start.
* Ollama/OpenWebUI: download update before stopping the service
Stage the release in <dir>.new while Ollama keeps running, stop the service
only for the directory swap. A failed or stalled download no longer leaves
the container without an Ollama binary. Restores the intent of #9894, which
was lost in the tools.func refactor (#14501).
* Remove inline comments
* immich: reuse prebuilt image-processing libraries from the base image
The installer compiles libjxl, jpegli, libheif, libraw, ImageMagick and
libvips from source, which takes 15min-2h. These are the same artifacts
Immich already ships in its ghcr.io/immich-app/base-server-dev base image.
Pull /usr/local out of that image (pinned by digest, parsed from the
release's server/Dockerfile) with daemonless skopeo + umoci and reuse it.
Verify vips is usable before committing to this path; on any failure, or
with IMMICH_LIBS_FROM_SOURCE=1, fall back to the unchanged source compile.
A version-matched ~/.immich_library_revisions is written so the update
script does not needlessly recompile the libraries.
* immich: keep build toolchain only in the source-compile fallback
Move the build-only toolchain (autoconf, automake, libtool, cmake, meson,
ninja-build, gcc-13) into the fallback branch and drop the unused ccache,
so the prebuilt-library path no longer installs them. The runtime library
-dev packages stay in the common path because they pull the shared
libraries the prebuilt libvips loads at runtime.
Also restore the base-images clone and source-dir creation in the fallback,
which the previous commit dropped.
* immich: update adds the Testing repo without debian.sources
Containers without /etc/apt/sources.list.d/debian.sources (Incus images) got
testing.sources from the install, but the update only looked in debian.sources
and ran sed on the missing file. Check every *.sources file, and write
testing.sources like the install does when debian.sources can't take it.
* immich: fall back to compiling when copying the prebuilt libraries fails
The tar copy out of the unpacked base image ran outside the if, so a failed or
partial unpack hit the ERR trap and aborted the install instead of compiling
from source.
* immich: use only the prebuilt image-processing libraries
Drop compiling libjxl, jpegli, libheif, libraw, ImageMagick and libvips from
source. The install pulls them from the base image the release's Dockerfile
pins and stops with a clear error when it can't (skopeo/umoci need Proxmox VE
9.1+). The update fetches and unpacks the new image before it stops or changes
anything, so a failure leaves the running install as it is, and installs it
only when the Immich release changes. ~/.immich_base_image records the image;
the old compile leftovers and ~/.immich_library_revisions are removed.
* Trilium: keep the installed version when an update download fails
update_script deleted /opt/trilium before fetch_and_deploy_gh_release, so a
failed download (GitHub answered 502 for the v0.107.0 archive) left the
container without Trilium, and every later update stopped at "No Trilium
Installation Found".
CLEAN_INSTALL=1 lets core clear the target only after the archive has
downloaded and extracted. If the deploy still fails, the service is started
again on the installed version and the pending marker makes the next update
retry. The install check now looks for trilium.service, so containers broken
by the old order recover with a plain update.
The "database" backup copied /opt/trilium/assets/db, which only holds files
shipped in the release; notes live in Trilium's data directory, which the
update never touches. Removed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TjCs8G7xWJ12fzC1g4v81E
* Trilium: back up the notes database before updating
With the service stopped and before the new release is deployed, the update
copies document.db (and a -wal file left by an unclean stop) to
<data dir>/backup/backup-before-update.db. The copy is kept after the update,
overwritten by the next one, and listed on Trilium's Backup page. If it cannot
be written, the update does not start and Trilium is restarted.
An install whose TRILIUM_DATA_DIR is inside /opt/trilium is refused before
anything is stopped, since CLEAN_INSTALL replaces that directory.
The install check accepts /opt/trilium again as well as trilium.service, so no
install that passed the old check fails the new one.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TjCs8G7xWJ12fzC1g4v81E
---------
Co-authored-by: s31teg <23174852+s31teg@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* OpenCloud: bump to v9.0.0, configure the service account through env
- Pin v9.0.0 in the update and install scripts.
- Copy the service account from opencloud.yaml into opencloud.env as
OC_SERVICE_ACCOUNT_ID/OC_SERVICE_ACCOUNT_SECRET, which every service
falls back to (covers 9.0's new auth_guest). Replaces the sed block
that inserted sharing.service_account into the YAML.
- Rename GRAPH_SPACES_DEFAULT_QUOTA to OC_SPACES_DEFAULT_QUOTA.
- Remove the unused thumbnails/files cache.
- Add a commented OC_ENABLE_GUEST_LINKS block to opencloud.env.
* OpenCloud: warn on install if the service account cannot be read
Same check as the update path, in case the opencloud init output changes.
* OpenCloud: name the FQDN variables literally for unattended installs
The prompt loop builds var_opencloud_<server>_fqdn at runtime, so the PR
script test found no variables to pre-answer and the install exited 64.
---------
Co-authored-by: Sim Kai Long <2094270+SimKaiLong@users.noreply.github.com>
Debian's nginx security update now passes HTTP_HOST as $host in fastcgi_params, which drops the port. Wallabag, Investbrain, Invoice Ninja, Poznote and WatchState then redirected to port 80 and the browser got connection refused. Pass $http_host again after the include.
openresty.org stalls or refuses for part of the users and is the top cause of NPM failures; Alpine's distfiles serve the same tarball (same sha256 for 1.29.2.5).
upstream stopped shipping backend/node_modules in the release tarball
for any arch as of 3.3.1, so amd64 installs crash on boot with
ERR_MODULE_NOT_FOUND. run npm ci unconditionally in install and update.