Skip to content

Port Syncthing appliance to TurnKey 19 - #12

Open
lirazsiri wants to merge 5 commits into
masterfrom
wish/syncthing-v19-trixie
Open

Port Syncthing appliance to TurnKey 19#12
lirazsiri wants to merge 5 commits into
masterfrom
wish/syncthing-v19-trixie

Conversation

@lirazsiri

Copy link
Copy Markdown
Member

Summary

  • port the Syncthing appliance to TurnKey 19 on Debian Trixie
  • update application installation, configuration, and runtime integration for the supported Trixie stack
  • add executable v19 smoke coverage and retain the accepted migration evidence

Validation

  • passed the configured Trixie root build in the Docker-based TKLDev 19 harness
  • passed noninteractive firstboot and the primary application workflow
  • passed dependency provenance and updater checks recorded in docs/v19.0-testing.md
  • git diff --check origin/master...HEAD

Use the Debian 13 Syncthing package and signed APT update channel instead of downloading a third-party repository key during the build. Preserve the dedicated service identity, firstboot credentials, localhost GUI binding, and Nginx TLS entry points while correcting device-key regeneration for the current Syncthing state layout.

Add functional acceptance coverage for normal boot, authenticated GUI and API access, default-folder indexing, proxy redirects, management services, and the supervised APT update path. Document the README contract crosswalk, Core inheritance, source choice, and deferred runtime tuning.
Allow the Syncthing acceptance check to recognize the spacing used by the Core Nginx SSL snippet. The first full Trixie run reached normal boot and healthy application services, then stopped because the test assumed one literal space in the directive.
Avoid a quiet grep pipeline that exits nonzero under the acceptance script pipefail contract. Validate the same system-certificate directive in the active inherited SSL snippet without changing appliance behavior or broadening runtime coverage.
Match the Angular application marker emitted by the Debian Trixie Syncthing UI. Version 1.29 binds the page title dynamically, so the legacy static title prefix caused the full runtime acceptance to reject an otherwise successful proxied response.
Bind the README crosswalk to the exact passing Docker acceptance run, behavioral source, installed package versions, and retained report hashes. This documentation-only commit preserves the already validated appliance behavior.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant