server/systemd-infrastructure
2
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity
Infrastructure for Podman containers and backing them up
16 commits 1 branch 0 tags 36 KiB
desktop 100%
Go to file
Fl1tzi 84b0a2bc8f Delete 'template_service.service'
2023-05-02 16:54:19 +00:00
backup-script@c16adbd4bc add submodule 2023-04-12 22:52:19 +02:00
.gitmodules add submodule 2023-04-12 22:52:19 +02:00
backup-schedule.timer Add 'backup-schedule.timer' 2023-04-12 22:12:07 +00:00
backup.service Add 'backup.service' 2023-04-12 22:11:36 +00:00
LICENSE Update 'LICENSE' 2023-04-12 01:34:05 +00:00
README.md add notice 2023-04-18 00:01:08 +02:00

README.md

lang
en-us

systemd-infrastructure

Infrastructure for Podman compose containers and backing them up (template)

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.

backup.service gets started by backup-schedule.timer on the schedule that is defined in backup-schedule.timer.

The backup script has to be configured correctly!

Template

The template_service is designed for containers and works well with the backup.