Add a share
- Dashboard
- CLI
Open Settings, then Network shares, and add a share. Choose NFS or CIFS and fill in the fields below.
Creating a share with credentials needs the control plane’s master key to be configured. Without one, the API refuses with a “not implemented” error. An NFS share carries no credentials.
Test, update and remove
testopens a TCP connection from the control plane to the share’s host on the protocol’s standard port (2049 for NFS, 445 for CIFS) with a 10 second timeout. A failure returns the address it could not reach. This is a reachability check only. It does not authenticate and never reads the CIFS password, so a passing test does not prove the credentials or the export path are right.updatetakes the full set of required fields again. Omit--passwordto keep the existing password; pass it to rotate it.deleteremoves the record. The control plane’s secrets store has no delete operation yet, so a deleted CIFS share’s encrypted password stays in the store, unreferenced.
--token, --api-url, --profile, --json, --output and --query flags.
API
A share does not appear on the project topology graph, because no stored link ties a share to an app volume.
Next steps
Backups and storage
Backup targets and volume backups.
App spec reference
Volumes and host-directory bind mounts.