Skip to content
This repository was archived by the owner on Oct 10, 2025. It is now read-only.

Commit a0062c9

Browse files
committed
docs: [#14] add comprehensive persistent volume documentation
- Add detailed comment explaining persistent data volume configuration - Clarify that /dev/vdb is the second disk attached for persistent storage - Document specific data types stored: database, config, SSL certs, logs, metrics - Explain data survival across VM destruction and infrastructure recreation - Improve maintainability and understanding of storage architecture This makes the cloud-init configuration self-documenting for the persistent data strategy implemented in the twelve-factor architecture.
1 parent 2cc9fb8 commit a0062c9

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

infrastructure/cloud-init/user-data.yaml.tpl

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,15 @@ users:
3333
# Disable SSH password authentication for security
3434
ssh_pwauth: false
3535

36-
# Disk and filesystem configuration
36+
# Persistent data volume configuration
37+
# This configures the second disk (/dev/vdb) attached to the VM for persistent storage.
38+
# All application data that needs to survive VM destruction is stored here, including:
39+
# - Database data (MySQL)
40+
# - Application configuration files (.env, tracker.toml)
41+
# - SSL certificates and keys
42+
# - Logs and application state
43+
# - Prometheus metrics data
44+
# The volume is mounted at /var/lib/torrust and survives infrastructure recreation.
3745
disk_setup:
3846
/dev/vdb:
3947
table_type: gpt

0 commit comments

Comments
 (0)