* 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
* 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>
* Add PVE LXC Apps Updater script and metadata
Add a new Proxmox LXC Apps Updater: frontend/public/json/update-apps.json registers the app for the UI (install script points to tools/pve/update-apps.sh) and provides documentation/notes for usage and environment variables. Add tools/pve/update-apps.sh (MIT, authors noted) — a full-featured updater for community-scripts managed LXC containers that supports interactive Whiptail selection or environment-driven automation (var_backup, var_backup_storage, var_container, var_unattended, var_skip_confirm, var_auto_reboot). Features include exportable JSON config, optional vzdump backups, detection of service/update script from the community repo, temporary CPU/RAM adjustments for build requirements, unattended update mode, restore-from-backup on failure, and reporting/optional reboot of containers that require it.
* Fix source command syntax in update-apps.sh
* Update tools/pve/update-apps.sh
Co-authored-by: Chris <punk.sand7393@fastmail.com>
* Update tools/pve/update-apps.sh
Co-authored-by: Chris <punk.sand7393@fastmail.com>
* Update tools/pve/update-apps.sh
Co-authored-by: Chris <punk.sand7393@fastmail.com>
* Update tools/pve/update-apps.sh
Co-authored-by: Chris <punk.sand7393@fastmail.com>
* Update tools/pve/update-apps.sh
Co-authored-by: Chris <punk.sand7393@fastmail.com>
* Update tools/pve/update-apps.sh
Co-authored-by: Chris <punk.sand7393@fastmail.com>
* Update tools/pve/update-apps.sh
Co-authored-by: Chris <punk.sand7393@fastmail.com>
* Update tools/pve/update-apps.sh
Co-authored-by: Chris <punk.sand7393@fastmail.com>
---------
Co-authored-by: Chris <punk.sand7393@fastmail.com>
- Add new SQL Server 2025 scripts with Ubuntu 24.04 support
- Refactor both versions to use setup_deb822_repo
- Fix debuginfod profile causing update errors (#11522)
- Use apt instead of apt-get in CT scripts
- Consistent messaging and formatting
