Skip to content

Port Concrete CMS appliance to TurnKey 19 - #26

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

Port Concrete CMS appliance to TurnKey 19#26
lirazsiri wants to merge 5 commits into
masterfrom
pr/v19-trixie

Conversation

@lirazsiri

Copy link
Copy Markdown
Member

Summary

  • port Concrete CMS to Debian Trixie and upstream 9.5.2
  • update installation, scheduler, firstboot configuration, and sitemap integration
  • add focused v19 acceptance for administrator login, page creation, persistence, services, and updater execution

Validation

  • independent review: SHIP at e14624d
  • retained run 20260825t073842z-5944-22398 passed build, firstboot, application flow, persistence, services, and updater execution before a wording-only test assertion
  • report SHA-256 a2cd8a01a32a5ed8d3ebb8d159028f5b5dff9ee85043d78f4a9c57046e018bd4 verified
  • git diff --check origin/master...e14624d

Concrete CMS is not packaged by Debian, so install the official 9.5.2 release asset and verify GitHub's published SHA-256 before extraction. Record the upstream tag commit and source metadata in the appliance.

Adapt the installer invocation to the current non-root CLI contract, use MariaDB 11-compatible account creation, preserve safe wrapper argument boundaries, and run the upstream scheduler through cron.

Add focused Docker acceptance for firstboot administrator login, page creation and persistence, jobs, scheduler, management endpoints, upstream update discovery, and signed Trixie package candidates. A disposable Trixie preflight completed the full 9.5.2 install on PHP 8.4.24 and MariaDB.
Concrete's path resolver has no HTTP site context in the focused CLI fixture, so resolving '/' produced a page object without a parent collection ID. Ask the site service for the default site's actual home page before creating the acceptance page.

Verified in disposable Debian Trixie with Concrete CMS 9.5.2, PHP 8.4 and MariaDB: page creation returned cID 269 and the path, title and HTML content all read back from the application database.
Concrete CMS 9 replaced the legacy generate_sitemap job with the c5:sitemap:generate command. Exercise that supported command, verify it writes sitemap XML, and retain the scheduler check without charging the stale test assertion against the appliance fix-loop budget.

Verified with bash syntax checks, shellcheck, and the official Concrete CMS 9 CLI and maintenance-task documentation.
Concrete CMS cannot infer a canonical site URL in a portable appliance. Pass the test HTTPS base URL to the supported sitemap command so the acceptance check exercises generation without imposing a deployment-specific hostname on users.

Verified with bash syntax checks, shellcheck, and the command contract emitted by Concrete CMS 9.5.2.
The supported c5:update command executed successfully, but its Concrete CMS 9.5 help text no longer contains the legacy phrase used by the acceptance grep. Check command availability by exit status and record the retained run that proved the primary appliance flows plus sitemap generation.

Verified with bash syntax checks, shellcheck, retained-evidence checksums, and the official GitHub latest-release API for Concrete CMS 9.5.2 and its published SHA-256.
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