Port ASP.NET Core appliance to TurnKey 19 - #7
Open
lirazsiri wants to merge 4 commits into
Open
Conversation
Move the sample to .NET 10 LTS from Microsoft's Debian 13 channel, verify the feed key, and retain MariaDB compatibility through exact EF Core 9 and Pomelo 9 dependencies with a locked restore. Remove unused global tools, protect generated database configuration, and pass forwarded HTTPS metadata from Nginx to Kestrel. Add focused acceptance for the sample, reverse proxy, EF-backed MariaDB data, service restart persistence, published dependency versions, and Microsoft and NuGet update discovery. Document the support boundary and pending exact-run evidence. Verified official feed and NuGet artifacts plus shell, schema, credential-rewrite, mode, diff, and documentation gates without invoking the blocked shared runner.
The Debian 13 feed is now signed by Microsoft's 2025 general signing key, so the appliance build rejected the repository while importing the older microsoft.asc key. Pin the current official key URL, full fingerprint, and content digest, and keep the acceptance assertion and documentation aligned. Verified the fetched key digest and fingerprint against the key shipped by Microsoft's current Debian 13 configuration package, plus bash syntax and diff checks.
The updater runs with pipefail, but its candidate parsers exited as soon as they saw the Candidate line. Microsoft packages expose a sufficiently long policy table for apt-cache to receive SIGPIPE and make the otherwise successful updater check exit 141. Read the complete policy output while preserving the same candidate value. Reproduced the old pipeline exit status 141 with a long policy table, verified the replacement exits zero with the same value, and checked Bash syntax and the Git diff.
Replace the deferred runner note with the authoritative passing run, tested source commit, retained report location and digest, and the main-flow behaviors exercised. Keep the documented command aligned with the shared builder used for the accepted run. Verified the retained report verdict and SHA-256, Bash syntax for the build and test scripts, ASCII-only documentation, and a clean diff.
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
Validation
2cf6f5b20260826t103646z-5508-23731passed for tested product0c089aa51c9528a4583819bfbaac5fd5c022c7cd931b77558841218a74cd192d52196c5verifiedgit diff --check origin/master...2cf6f5b