Role
Enabled by default
WP content NFS storage in the WordPress stack
This page explains what WP content NFS storage means in the WordPress stack: how it is included, which base service it uses, and how it connects to the rest of the stack.
WP content NFS storage is enabled by default in instances created from the WordPress stack, but it is not treated as a core required service.
Base service
Ganesha NFS provisioner
Type
storage
Stack fit
How WP content NFS storage fits into this stack
WP content NFS storage is enabled by default in instances created from the WordPress stack, but it is not treated as a core required service.
This stack service is based on Ganesha NFS provisioner and keeps the service-specific setup for WordPress in one place.
Version policy
Available versions include 4.
Inclusion
Enabled by default: Yes
Required: No
Primary: No
Connections
No explicit service links are defined for this stack service.
Storage
data: 25 GB
Stack-specific technical details
Review the operational capabilities exposed by WP content NFS storage inside this stack, including backups, imports, configs, settings, cron, actions, storage, and service links where they exist.
Backups
Protect service data with repeatable backup workflows that stay attached to the stack.
Files backup
Imports and migration
Bring working data into another environment or onboard existing workloads faster with stack-defined import flows.
Files import
Import from a backup archive, uploaded file, or public URL depending on the service workflow.
Volumes
Provision the persistent storage and shared volume relationships the stack expects.
Data