How grafl/skeleton works
Skeleton has two independent runtime paths: a console APR/APR-util demonstration and a local Apache server with a custom request handler. The server path serves static content and Apache diagnostics as well as the library-backed /test response. The README documents these routes and the load configuration; src/mod_test.c and the server configuration template were not excerpted, so their internal routing details are shown only as documented.
Main entry points: main.c Skeleton console · mod_test.c Test handler · test1.c Message library · httpd-test.conf.in Test server config
Components 12
Console demonstration
- Skeleton console
src/main.c - APR runtime
- APR-util Base64
Local HTTP server
- Apache httpd
- Test server config
cmake/httpd-test.conf.in - Sample page
cmake/httpd-test-index.html - Server diagnostics
Custom response
- Test handler
src/mod_test.c - Message library
src/test1.c - Shared APR
Other components
- Console user
- HTTP client
Connections 10
- Console user → Skeleton console: runs
README.md - Skeleton console → APR runtime: initializes and allocates
src/main.c - Skeleton console → APR-util Base64: Base64 encodes
src/main.c - HTTP client → Apache httpd: sends requests
README.md - Test server config → Apache httpd: configures
README.md - Apache httpd → Sample page: serves at /
README.md - Apache httpd → Test handler: dispatches /test
README.md - Test handler → Message library: calls message function
README.md - Message library → Shared APR: allocates from pool
README.md - Apache httpd → Server diagnostics: dispatches /server-info
README.md