add notice
This commit is contained in:
parent
0b043ab1ba
commit
afaea1cf9d
17
README.md
17
README.md
|
@ -1,8 +1,16 @@
|
|||
---
|
||||
lang: en-us
|
||||
---
|
||||
|
||||
# systemd-infrastructure
|
||||
|
||||
Infrastructure for Podman(-compose) containers and backing them up (template)
|
||||
Infrastructure for Podman compose containers and backing them up (template)
|
||||
|
||||
## backup
|
||||
## Why podman-compose?
|
||||
|
||||
It just works for me. But because of the not really native support I would eventually move to kube configurations.
|
||||
|
||||
## Backup
|
||||
|
||||
Both `backup.service` and `backup-schedule.timer` need to be present in the systemd user folder.
|
||||
|
||||
|
@ -10,6 +18,7 @@ Both `backup.service` and `backup-schedule.timer` need to be present in the syst
|
|||
|
||||
**The backup script has to be configured correctly!**
|
||||
|
||||
## template
|
||||
## Template
|
||||
|
||||
The `template_service` is designed for containers and works well with the backup.
|
||||
|
||||
The `template_service` is designed for containers and works well with the backup.
|
Loading…
Reference in a new issue