Stacks/Zammad/Services

Zammad stack services

This page shows the capabilities provided by the services in the Zammad stack and the connections, configs, settings, cron schedules, actions, volumes, backups, imports, and other customizations attached to them for this specific stack.

Stack serviceBase serviceVersionsRole
Zammad7.2Primary
PostgreSQL18, 17Required
Redis8.6, 8.4, 8.2Required
Memcached1.6Required
Elasticsearch9.5Enabled by default
OpenSMTPD7Enabled by default
  • Additional services can be added or removed.
  • When one of the services in the stack updates, the stack can be upgraded to a new revision.
  • Stack changes can then be rolled out to environments on your schedule.

Backups

Protect service data with repeatable backup workflows that stay attached to the stack.

PostgreSQL
Default database backup

Imports and migration

Bring working data into another environment or onboard existing workloads faster with stack-defined import flows.

PostgreSQL
Database import
Import from a backup archive, uploaded file, or public URL depending on the service workflow.

Configs

Keep service config files versioned with the stack instead of rebuilding them per environment.

PostgreSQL
PostgreSQL config
PostgreSQL
PostgreSQL config

Settings

Tune service behavior per environment while keeping one reusable stack baseline.

Zammad
Administrator email
Zammad
Administrator first name
Default value: Admin.
Zammad
Administrator last name
Memcached
Cache memory (MB)
Default value: 64.
Memcached
Worker threads
Default value: 4.
Memcached
Maximum connections
Default value: 1024.

Volumes

Provision the persistent storage and shared volume relationships the stack expects.

Size: 10 GB.
Redis
Data
Optional.
Elasticsearch
Elasticsearch data
Size: 20 GB.
Optional.