Update frontend metadata (config path, interface port, and expanded description) and modernize the install script: switch apt-get to apt, streamline dependency list (remove wget/jq/unzip), replace inline hardware-acceleration/GPU group tweaks with setup_hwaccel, pin Frigate release to v0.16.4 for reproducible installs, and fetch/libusb build now uses fetch_and_deploy_gh_release with adjusted paths. Also clean up removed temporary files.
Add frontend metadata for Frigate (frontend/public/json/frigate.json), remove the old .bak metadata file, and perform a major refactor of install/frigate-install.sh. The installer now targets Debian 12 (Bookworm), converts APT sources to deb822, installs and builds required dependencies (Python wheels, libusb, OpenVINO, Tempio, Nginx, sqlite extensions), configures hardware acceleration and GPU access, fetches and deploys Frigate and go2rtc releases, and prepares inference/audio models. Systemd service units were improved (dependencies, env file usage, safer log file handling, create_directories service) and services are enabled/started with cleanup steps added. Also updated copyright/authorship and various runtime environment exports and default Frigate config changes (ffmpeg hwaccel, detector selection, disabled auth/detect in default config).
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>
* 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
* Downgrade OpenProject and NginxProxyManager to Debian 12 due to SHA1 signature issues
* Downgrade Semaphore to Debian 12 due to SHA1 signature issues in Ansible PPA
Allow users to import scripts into the JSON editor via local file
upload or by selecting from the existing script library.
- Dropdown toggle for 'Local' and 'Library' import sources.
- Script selection dialog with category and search filters.
- Global search using the existing command menu logic.
CanbiZ (MickLesk)