Role
Enabled by default
Mailpit in the Laravel stack
This page explains what Mailpit means in the Laravel stack: how it is included, which base service it uses, and how it connects to the rest of the stack.
Mailpit is enabled by default in instances created from the Laravel stack, but it is not treated as a core required service.
Base service
Mailpit
Type
service
Stack fit
How Mailpit fits into this stack
Mailpit is enabled by default in instances created from the Laravel stack, but it is not treated as a core required service.
This stack service is based on Mailpit and keeps the service-specific setup for Laravel in one place.
Version policy
Available versions include 1.20.
Inclusion
Enabled by default: Yes
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 Mailpit inside this stack, including backups, imports, configs, settings, cron, actions, storage, and service links where they exist.
Volumes
Provision the persistent storage and shared volume relationships the stack expects.
Data
Optional.