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(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>
* Replace build:sqlite with db:generate + build
Update build flow in ct/pangolin.sh and install/pangolin-install.sh to use `npm run db:generate` followed by `npm run build` instead of the old `npm run build:sqlite`. Also normalize a DB generation invocation by replacing `npm run db:sqlite:generate` with `npm run db:generate` in the installer. These changes consolidate DB generation and use the standard build step.
* Update pangolin-install.sh
* db push on update
- 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
* Add writefreely (ct)
* Create symlink for WriteFreely in /usr/local/bin
Added symbolic link for WriteFreely executable
* Fix date_created and update user creation instructions
Updated the creation date and modified user creation instructions.
* Create symlink for WriteFreely in /usr/local/bin
Added a symbolic link for the WriteFreely executable.
---------
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>
Simplify the Web-Vault update flow by creating /opt/vaultwarden/web-vault and calling fetch_and_deploy_gh_release with that path as the deployment target. Removes temporary directory creation, move and cleanup (mktemp/mv/rm -rf) and ensures the destination exists before downloading. Ownership and the success message are preserved.
Deploy the Web-Vault release into a temporary directory before moving it into /opt/vaultwarden. The change creates a mktemp -d directory, passes that to fetch_and_deploy_gh_release, moves the extracted web-vault into /opt/vaultwarden/web-vault, and removes the temp dir. This prevents partial or mixed artifacts in /opt during the fetch/extract step and keeps the existing ownership/chown behavior.
