Research notes: Moodle on Keel Web (Nginx and PHP-FPM) #1

New issue

Open

opened 2026-10-03 10:59:23 -03:00 by marcos-mendez · 0 comments

marcos-mendez commented

2026-10-03 10:59:23 -03:00

(Migrated from github.com)

Context
This repository is the TurnKey Moodle recipe (Apache). Keel is moving applications onto Keel Web (Nginx with PHP-FPM), and Moodle is not packaged in Debian, so a port needs research first. This is research only, no code.

What to do
Post a comment on this issue that answers, with a link for each fact:

The current Moodle LTS and latest release, and their PHP version requirements; whether trixie's PHP (8.4) is supported.
The PHP extensions Moodle requires, mapped to Debian 13 package names.
The Nginx configuration Moodle documents (the slasharguments path info handling, and whether the web root moved, for example to a public/ directory, in recent releases).
The moodledata directory: where it should live and why it must be outside the web root.
The CLI installer (admin/cli/install.php): which values a first-boot screen would have to ask for (admin password, email, site name, domain).
The cron requirement (admin/cli/cron.php) and how often it must run.
What the current recipe in this repository (plan/, conf.d/, overlay/) does that a Keel Web port would still need.
Open questions.

Done when
The notes are posted here, each point has a source, and the open questions are listed.

Help
Ask in https://github.com/orgs/Keel-Linux/discussions

**Context** This repository is the TurnKey Moodle recipe (Apache). Keel is moving applications onto Keel Web (Nginx with PHP-FPM), and Moodle is not packaged in Debian, so a port needs research first. This is research only, no code. **What to do** Post a comment on this issue that answers, with a link for each fact: 1. The current Moodle LTS and latest release, and their PHP version requirements; whether trixie's PHP (8.4) is supported. 2. The PHP extensions Moodle requires, mapped to Debian 13 package names. 3. The Nginx configuration Moodle documents (the `slasharguments` path info handling, and whether the web root moved, for example to a `public/` directory, in recent releases). 4. The `moodledata` directory: where it should live and why it must be outside the web root. 5. The CLI installer (`admin/cli/install.php`): which values a first-boot screen would have to ask for (admin password, email, site name, domain). 6. The cron requirement (`admin/cli/cron.php`) and how often it must run. 7. What the current recipe in this repository (`plan/`, `conf.d/`, `overlay/`) does that a Keel Web port would still need. 8. Open questions. **Done when** The notes are posted here, each point has a source, and the open questions are listed. **Help** Ask in https://github.com/orgs/Keel-Linux/discussions