Skip to content

Port e107 appliance to TurnKey 19 - #21

Open
lirazsiri wants to merge 6 commits into
masterfrom
wish/e107-v19-trixie
Open

Port e107 appliance to TurnKey 19#21
lirazsiri wants to merge 6 commits into
masterfrom
wish/e107-v19-trixie

Conversation

@lirazsiri

Copy link
Copy Markdown
Member

Summary

  • port the e107 appliance to TurnKey 19 on Debian Trixie
  • update application installation, configuration, and runtime integration for the supported Trixie stack
  • add executable v19 acceptance 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
  • independent execution and PR-scope review returned SHIP
  • git diff --check origin/master...cf57530c0ab0e139e8607d8b7dfdcd0e9ddb809e

Replace the obsolete SourceForge download with the maintained official e107 release and verify its archive digest. Update the installer for PHP 8.4 and current MariaDB, and make firstboot store administrator credentials with PHP's supported password hashing API.

Add focused Docker acceptance coverage for boot, TLS, administrator login, database state, cron, management services, and the supported upstream update channel.
The installer helper is intentionally called once without form data to obtain the first workflow token. Under nounset, reading the missing positional argument aborted the appliance build before the request ran.

Treat the first payload as empty while preserving the existing staged installation sequence. Verified with shell syntax checks and diff hygiene; exact appliance acceptance follows.
After the installer correction, the exact candidate completed the upstream installation, built, booted, ran firstboot, and reached healthy services. Its app-local runtime test then exited without recording which silent assertion failed.

Add a concise ERR marker for one later diagnostic acceptance run. This changes only test observability and does not consume another product fix loop.
Follow e107's successful login redirect so acceptance inspects the authenticated response instead of the empty redirect body. Create a public news item through the CSRF-protected administrator form, then verify its MariaDB state and public rendering.

Replace the dead upgrade guide with the live official release channel, require its matching v2.x upgrade asset and SHA-256 digest, and cite the retained Core 19 baseline. Verified with shell syntax and diff checks plus a disposable Trixie e107 2.3.11 probe covering login, content creation, database persistence, public read, and release metadata parsing.
The exact runtime test required a versioned PHP metapackage that the appliance plan does not install, even though Debian resolves the planned PHP CLI and extension packages to PHP 8.4. Check the plan's stable package names so acceptance continues into the user-facing runtime and updater evidence.

Verified with bash syntax checking and git diff hygiene.
Record the passing exact run for the Trixie appliance, including the main-flow behaviors, installed versions, fix-loop usage, and retained artifact digests. Replace the earlier pending gate with the final Docker acceptance boundary.

Verified with the exact appliance harness, shell syntax checks, documentation character checks, and git diff hygiene.
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