Replace the final '| head -1' in both install and ct scripts with 'awk 'NR==1'' to pick the first matching Teamspeak release line. In the ct script the previous temporary toggling of pipefail was also removed, simplifying the command. This improves compatibility and reduces reliance on an extra utility in minimal environments.
Update scripts to use Python 3.12 for uv tool setup and Open-WebUI installs/upgrades. Add a numba constraint (--constraint <(echo "numba>=0.60")) to uv tool install/upgrade commands to ensure compatibility. Changes applied to ct/openwebui.sh and install/openwebui-install.sh for both fresh installs and update paths.
Replace npm script calls to db:sqlite:generate and db:sqlite:push with db:generate and db:push in ct/pangolin.sh and install/pangolin-install.sh. This makes the build/install steps use the generic DB task names for consistency across update and install workflows.
EMQX 6.1+ preallocates significant disk space for the MQ feature,
causing high CPU/disk usage on small containers (emqx/emqx#16649).
- Increase default disk from 4GB to 6GB
- Add read -rp prompt during install to optionally disable MQ feature
via mq.enable=false in emqx.conf (reduces disk/CPU overhead)
- Setting is in install script (not CT script) per reviewer feedback
Co-authored-by: sim-san <sim-san@users.noreply.github.com>
Kasm changed their release URL format starting with v1.18.1:
- Old format: kasm_release_1.18.0.09f70a.tar.gz (with hash)
- New format: kasm_release_1.18.1.tar.gz (without hash)
The script now tries both detection methods:
1. First tries to find URL with hash suffix (old format)
2. Falls back to detecting version from service_images URLs and
constructing the new URL format
This fixes the update detection for Kasm v1.18.1 and future versions.
Fixes#11785
The install script overwrote the correct appsettings.json shipped in the
release archive with a hardcoded copy that was missing newer required
fields (ApiKey, ProxyPort, EnableChangedTitleCache) and had structural
differences (Lidarr/Readarr as arrays instead of objects), causing the
service to fail on startup.
- Remove hardcoded appsettings.json from install script (release archive
already ships the correct version)
- Backup and restore appsettings.json during updates to preserve user
configuration
Closes#11665
* fix(nginx-ui): remove admin user hack, use setup wizard instead
The previous install script started nginx-ui for 3 seconds, stopped it,
and ran reset-password to create an admin user. This caused:
- Race condition: the internal setup wizard could trigger during the brief
start window, conflicting with the reset-password approach
- Admin users unable to login after the setup wizard fired
- Settings lockup due to overloaded app.ini with hardcoded nginx paths
that conflict with UI-managed settings
Changes:
- Remove start/stop/reset-password hack from install script
- Simplify app.ini to match upstream defaults (minimal config)
- Let users complete the natural setup wizard on first visit
- Update JSON: remove default credentials, add setup wizard note
- Add setup wizard hint to CT script output
The setup wizard properly handles admin account creation and ACME email
configuration, which are both needed for full functionality.
Ref: ProxmoxVED#1408
* Update nginx-ui.sh
* fix(nginxproxymanager): update for better-sqlite3 and setup wizard
NPM switched to better-sqlite3 as the knex database client.
The old sqlite3 client causes 'Internal Error' on user creation.
- Update production.json in install/update to use better-sqlite3
- Add sed patch in update script to fix existing production.json
- Add useNullAsDefault: true to match upstream knex config
- Remove default credentials from JSON (NPM now uses setup wizard)
- Add note about setup wizard for first-time users
Ref: NginxProxyManager/nginx-proxy-manager@0b2fa82Closes#11681
* Update nginxproxymanager.json
* Remove disabled script error messages
Removed error messages related to OpenResty APT repository issues.
* Pin NocoDB to version 0.301.1 due to ipaddr.js module error in 0.301.2
* Pin NocoDB version to 0.301.1 in github-versions.json
* Remove version pin note from nocodb.json (handled in github-versions.json)
* Add version pin to check_for_gh_release in NocoDB CT
Prevents the update check from looking for versions newer than 0.301.1
* Pin Memos to v0.25.3 - last version with release binaries
v0.26.0 removed release binaries (issue usememos/memos#5552)
Pinning to v0.25.3 (Nov 25, 2025) which has 7 binary assets available
This is a temporary solution until v0.27.0 releases with binaries
as indicated by MickLesk in issue #11474
* Pin Memos scripts to v0.25.3 instead of latest
Both CT update script and install script now explicitly use v0.25.3
instead of 'latest' to ensure binaries are available
* Add version pin to check_for_gh_release in Memos CT
Prevents the update check from looking for versions newer than v0.25.3
* Add nightscout (ct)
* Change fetch_and_deploy_gh_release to use tarball
* Modify date_created and logo in nightscout.json
Updated the creation date and logo URL for Nightscout.
* Change fetch method from source to tarball
* Update nightscout.json
---------
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>
Co-authored-by: Tobias <96661824+CrazyWolf13@users.noreply.github.com>
