mirror of
https://github.com/funkypenguin/geek-cookbook/
synced 2025-12-13 09:46:23 +00:00
Add Duplicity, fix gitlab
This commit is contained in:
17
manuscript/reference/data_layout.md
Normal file
17
manuscript/reference/data_layout.md
Normal file
@@ -0,0 +1,17 @@
|
||||
# Data layout
|
||||
|
||||
The applications deployed in the stack utilize a combination of data-at-rest (_static config, files, etc_) and runtime data (_live database files_). The realtime data can't be [backed up](/recipies/duplicity) with a simple copy-paste, so where we employ databases, we also include containers to perform a regular export of database data to a filesystem location.
|
||||
|
||||
So that we can confidently backup all our data, I've setup a data layout as follows:
|
||||
|
||||
## Configuration data
|
||||
|
||||
Configuration data goes into /var/data/config/[recipe name], and is typically only a docker-compose .yml, and a .env file
|
||||
|
||||
## Runtime data
|
||||
|
||||
Realtime data (typically database files or files-in-use) are stored in /var/data/realtime/[recipe-name], and are **excluded** from backup (_They change constantly, and cannot be safely restored_).
|
||||
|
||||
## Static data
|
||||
|
||||
Static data goes into /var/data/[recipe name], and includes anything that can be safely backed up while a container is running. This includes database exports of the runtime data above.
|
||||
@@ -14,4 +14,4 @@ Network | Range
|
||||
[Unifi](https://geek-cookbook.funkypenguin.co.nz/recipies/unifi/) | 172.16.7.0/24
|
||||
[Kanboard](https://geek-cookbook.funkypenguin.co.nz/recipies/kanboard/) | 172.16.8.0/24
|
||||
[Gollum](https://geek-cookbook.funkypenguin.co.nz/recipies/gollum/) | 172.16.9.0/24
|
||||
[Wallabag](https://geek-cookbook.funkypenguin.co.nz/recipies/wallabag/) | 172.16.10.0/24
|
||||
[Duplicity](https://geek-cookbook.funkypenguin.co.nz/recipies/duplicity/) | 172.16.10.0/24
|
||||
|
||||
Reference in New Issue
Block a user