Upstream confirmed in scanopy/scanopy#698 that scanopy-server-linux-*
has carried the built UI since v0.17.13, fixtures and service logos
included, served on the same port as the API. The release notes never
said so, which is why we kept building it.
That removes the source tarball, the Rust toolchain and
generate-fixtures, Node with npm ci and npm run build, and
SCANOPY_WEB_EXTERNAL_PATH. With the variable set to a directory that no
longer has an index.html, v0.17.14 and earlier refuse to start, so the
update deletes the line rather than leaving it. build-essential,
libssl-dev and pkg-config go too: the release binary is static-pie with
no INTERP segment, so it has no runtime library dependencies.
/opt/scanopy stays, now only for .env and oidc.toml, and the unit's
WorkingDirectory follows it out of the removed backend directory. Since
nothing wipes that directory any more, the config survives an update on
its own, which is the report upstream passed on of an update coming
back without SCANOPY_WEB_EXTERNAL_PATH and the server starting API-only.
The update keeps the running binary until the new one answers
/api/health and puts it back if it does not, so a bad release leaves a
working server instead of a stopped one.
check_for_gh_release now keys on scanopy-server, matching the version
file the binary deploy writes; the Scanopy key belonged to the tarball
that is gone. Existing containers run one extra update, then agree.
Adds five optional var_jitsi_* settings to the install script. All default
to empty, which keeps the previous LAN-only behaviour (container IP,
self-signed certificate):
- var_jitsi_domain public hostname instead of the container IP
- var_jitsi_le_email Let's Encrypt via the packaged debconf option
- var_jitsi_public_ip static NAT mapping in jvb.conf (JVB 2.3+)
- var_jitsi_admin_user secure domain: only authenticated users create rooms
- var_jitsi_admin_pass password for that user (generated when empty)
Tested on Proxmox VE 9.2 as unprivileged Debian 13 LXC, both with all
variables set (self-signed) and with none set.
Co-authored-by: klanghans <13657862+klanghans@users.noreply.github.com>
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
* Add gotenberg (ct)
* Update messages in gotenberg.sh for clarity
* Implement unoconverter update in gotenberg.sh
* Fix formatting and add Go version setup in script
* Update Gotenberg installation script for Go version
---------
Co-authored-by: push-app-to-main[bot] <203845782+push-app-to-main[bot]@users.noreply.github.com>
Co-authored-by: Tobias <96661824+CrazyWolf13@users.noreply.github.com>
* Add chevereto (ct)
* Update var_arm64 default value and cleanup messages
Changed default value of var_arm64 to 'yes' and removed setup completion message.
* Remove ffmpeg installation and add setup_ffmpeg call
* chevereto: derive php-fpm from one version, use nginx_enable_site
* chevereto: drop php modules already covered by setup_php
---------
Co-authored-by: push-app-to-main[bot] <203845782+push-app-to-main[bot]@users.noreply.github.com>
Co-authored-by: CanbiZ (MickLesk) <47820557+MickLesk@users.noreply.github.com>
* Add logseq (ct)
* logseq: provision corepack via setup_nodejs, use nginx helper, set up toolchains on update
---------
Co-authored-by: push-app-to-main[bot] <203845782+push-app-to-main[bot]@users.noreply.github.com>
Co-authored-by: MickLesk <47820557+MickLesk@users.noreply.github.com>
composer's root/superuser safety prompt blocks on stdin during update_script,
since the container's terminal isn't attached to answer it. Set
COMPOSER_ALLOW_SUPERUSER=1 to suppress the prompt, matching composer's
documented approach for running as root non-interactively.
* Add matter-hub (ct)
* Enable ARM64 support by default in matter-hub.sh
* Remove Home Assistant setup instruction
Removed instruction to set Home Assistant URL and token.
---------
Co-authored-by: push-app-to-main[bot] <203845782+push-app-to-main[bot]@users.noreply.github.com>
Co-authored-by: CanbiZ (MickLesk) <47820557+MickLesk@users.noreply.github.com>
MickLesk