Port Torrentserver appliance to TurnKey 19 - #21
Open
lirazsiri wants to merge 3 commits into
Open
Conversation
Move the appliance to Debian's Transmission 4 package series and make its authenticated RPC, storage, peer port, ClamAV completion hook, and service dependencies explicit. Remove stale rTorrent and nginx residue that no longer participates in the Apache-based product. Pass the firstboot password over standard input and replace Transmission settings atomically so credentials do not appear in process arguments and a failed write cannot leave a truncated configuration. Add a focused local torrent lifecycle and Samba round-trip probe, HTTPS and service checks, signed Debian APT update evidence, and the Wave 2 crosswalk. Verified against the exact Trixie Transmission package in a disposable no-tracker probe, plus shell and Python syntax, diff hygiene, result protocol, credential scans, and completion-hook failure boundaries.
Debian's ClamAV unit refuses to start until both main and daily databases exist. On a fresh appliance, freshclam creates them after systemd has already skipped the daemon, leaving Transmission's completion hook unavailable until reboot. Watch the database directory and start the stock daemon after the first update. Keep freshclam and the watcher supervised, and allow the focused acceptance probe to wait for the asynchronous first download. Verified with shell and Python syntax checks, the seven-field result protocol, diff hygiene, and systemd-analyze against the Debian Trixie 1.4.3 units.
Replace the stale infrastructure blocker with the passing exact Docker run and map each appliance-defining README claim to observed runtime evidence. Record the signed Trixie update result, configured-root fallback boundary, deferred malware-signature exercise, and final fix-loop accounting. Verified against run 20260826t051321z-3895-9520, including its retained report and seven-field child result.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Source and update path
Validation
20260826t051321z-3895-95200e8feb584d6ef8c8c753f64a7302b3da7f45095189fd0d930f3f79e9a4bd5fdbThe exact behavioral build used source commit
b8a18fe3aab39e6871d304f440bf1b2b27b9939a. The accepted PR tip adds the reviewed evidence and testing-documentation delta recorded in the commit history.Known limitation: Docker runtime does not exercise installer, kernel, or hardware behavior. The Docker kernel rejects the appliance hostname firstboot call and systemd-sysctl unit; application services are checked explicitly.
The Docker acceptance exercises the normal systemd and firstboot path, primary authentication, identity-defining behavior, persistence, required services, package provenance, and updater evidence. It deliberately does not repeat ISO or installer testing because the Core/TKLDev v19 format path was exercised separately.