HarvTTP web server
HarvTTP is the first HarvOS server service. The boot ROM loads
harvttp.elf from the program USB image, the server obtains
an address through DHCP, listens on port 80 and serves the web root
through the CPU-real HNET path.
Core properties
ELF based
HarvTTP is not a host-side HTTP server. In the hardware test path the boot ROM validates the ELF, places its segments into IMEM and DMEM and then jumps into the application entry point.
Static and dynamic web roots
The loader can preload static assets from
/confg/harvttp/httproot. The PHP-enabled path also
serves a data-image web root for larger WordPress-oriented file
trees.
Cooperative service workers
Internal workers handle content initialization, DHCP, TX pumping, RX/HTTP dispatch, watchdog telemetry and PHP request execution. They share one small freestanding runtime today.
PHP and SQL integration
HarvTTP contains the HTTP side for PHP 8.5/Zend experiments. HarvSQL provides the MySQL-compatible database service intended for PHP and WordPress tests.
What this proves
HarvTTP demonstrates that the HarvOS boot path can load real ELF services and that those services can drive network traffic through the SoC MMIO device rather than a hidden host socket. It is intentionally small: the current stack focuses on observable CPU, memory, boot and HNET behavior before growing into a production HTTP server.
Documentation pages
| Page | Scope |
|---|---|
| Operation | Start parameters, worker model, request dispatch, PHP execution and path rules. |
| Network | DHCP, ARP, IPv4, TCP, HNET MMIO and test-network access. |
| Setup | Build commands, USB image layout, PHP/Zend builds, WordPress files and browser checks. |
| PHP 8.5 | HarvOS SAPI, Zend request flow, worker queue, WordPress profile and runtime caveats. |
| HarvSQL | SQL server ELF, MySQL protocol support, seed/migration scripts, storage and limits. |
| Limits | Known bottlenecks, production risks and the recommended supervisor/network architecture. |