Role
Disabled by default
Apache HTTP Server in the HTML stack
This page explains what Apache HTTP Server means in the HTML stack: how it is included, which base service it uses, and how it connects to the rest of the stack.
Apache HTTP Server is available in the HTML stack but starts disabled, so teams can turn it on only when a specific app needs it.
Base service
Apache HTTP server
Type
service
Delivery
Boilerplate or your repository
Stack fit
How Apache HTTP Server fits into this stack
Apache HTTP Server is available in the HTML stack but starts disabled, so teams can turn it on only when a specific app needs it.
This stack service is based on Apache HTTP server and keeps the service-specific setup for HTML in one place.
Version policy
Available versions include 2.4.
Delivery
Start from a boilerplate or connect your repository
Apache HTTP Server includes a ready starting point for the HTML stack.
HTML boilerplate
Use this boilerplate as a working starting point for your application.
wodby/html-boilerplateInclusion
Enabled by default: No
Required: No
Primary: No
Connections
No explicit service links are defined for this stack service.
Storage
This stack service does not define persistent volume sizes.
Stack-specific technical details
Review the operational capabilities exposed by Apache HTTP Server inside this stack, including backups, imports, configs, settings, cron, actions, storage, and service links where they exist.
Configs
Keep service config files versioned with the stack instead of rebuilding them per environment.
Main
Virtual host
Settings
Tune service behavior per environment while keeping one reusable stack baseline.
Apache docroot subdir