fediversity/fediversity

Watch

Fork 10

Operator can make back-ups of applications' mutable file systems #126

New issue

Open

opened 2025-02-12 09:18:39 +01:00 by kiara · 4 comments

kiara commented

2025-02-12 09:18:39 +01:00

Owner

As an operator,
given I run Fediversity applications,
I want to be able to make back-ups of applications' mutable file systems,
in order to rest assured I will not lose important data.

implementation notes

May be handled using SelfHostBlocks' Backup Contract.

**As** an operator, **given** I run Fediversity applications, **I want** to be able to make back-ups of applications' mutable file systems, **in order to** rest assured I will not lose important data. ## implementation notes May be handled using SelfHostBlocks' [Backup Contract](https://shb.skarabox.com/contracts-backup.html).

kiara added a new dependency

2025-02-12 09:22:15 +01:00

#123 enable back-ups of application

kiara referenced this issue

2025-06-01 19:38:34 +02:00

enable back-ups of applications' immutable storage #125

kiara added the

type: user story

label

2025-06-02 12:05:39 +02:00

kiara added a new dependency

2025-06-08 13:19:05 +02:00

#138 VMs use central file storage

~~kiara referenced this issue 2025-06-09 14:11:42 +02:00~~

application offering delegated #369

kiara referenced this issue

2025-09-11 17:42:33 +02:00

enable back-ups of application #123

kiara referenced this issue

2025-12-02 15:43:01 +01:00

applications imported from contract-based implementations #601

kiara added the

3 points

label

2025-12-02 20:31:28 +01:00

kiara commented

2026-06-06 22:46:50 +02:00

Author

Owner

@Toast has wondered if our applications' state might not all already be in just DBs + S3.
to verify, we might say check the applications' dataDir.

@Toast has wondered if our applications' state might not all already be in just DBs + S3. to verify, we might say check the applications' `dataDir`.

kiara added a new dependency

2026-06-06 22:49:33 +02:00

#29 Backups for Forgejo

Toast commented

2026-06-07 18:17:13 +02:00

Member

Indeed!

So far for the operator applications we currently support (mastodon, peertube, pixelfed), most seem to use S3 storage exclusively. However, with peertube, the documentation is not the clearest about it.

https://docs.joinpeertube.org/maintain/remote-storage#remote-storage-s3 mentions this:

Live videos are still stored on the disk. If replay is enabled, they will be moved in the object storage after transcoding.

Indeed! So far for the operator applications we currently support (mastodon, peertube, pixelfed), most seem to use S3 storage exclusively. However, with peertube, the documentation is not the clearest about it. https://docs.joinpeertube.org/maintain/remote-storage#remote-storage-s3 mentions this: > Live videos are still stored on the disk. If replay is enabled, they will be moved in the object storage after transcoding.

❤️ 1

Toast commented

2026-06-07 18:38:32 +02:00

Member

For peertube, the migration guide mentions backing up two directories

/var/lib/peertube/config
Should contain NixOS generated files exclusively, however after checking that directory on out tests, there's also a local.yaml
with some sort of secret.
Edit: this secret is already handled
/var/lib/peertube/storage
We use S3 so it should be empty, however peertube creates the file structure it would have if we used file storage instead.
I inspected it after running the tests too, and it does leave some files over
I am unfamiliar with peertube so I don't know if this data would be regenerated on startup, or as needed (with thumbnails), so I don't know if it's worth backing up

For peertube, the migration guide mentions backing up two directories 1. `/var/lib/peertube/config` ~~Should contain NixOS generated files exclusively, however after checking that directory on out tests, there's also a `local.yaml` with [some sort of secret](https://github.com/Chocobozzz/PeerTube/blob/f78c01f0b51359220f5d717bc662685712c43ddd/config/default.yaml#L17).~~ Edit: this secret is already handled![image](/attachments/4e40e611-ce80-40e4-a57b-c018e2e2c16d) 2. `/var/lib/peertube/storage` We use S3 so it should be empty, however peertube creates the file structure it would have if we used file storage instead. I inspected it after running the tests too, and it does leave some files over ![image](/attachments/8febef00-a9f3-4cb0-95c7-f4fa254bea23) I am unfamiliar with peertube so I don't know if this data would be regenerated on startup, or as needed (with thumbnails), so I don't know if it's worth backing up

image.png

128 KiB

image.png

78 KiB

Toast commented

2026-06-07 19:14:42 +02:00

Member

For pixelfed, the documentation is severely lacking in this regard, so I have no backup or migration guide available.
However, from looking at the files in /var/lib/pixelfed, we might want to back them up, since there's some keys there (and also a lot of .gitignore files that I'm excluding here):

For pixelfed, the documentation is severely lacking in this regard, so I have no backup or migration guide available. However, from looking at the files in `/var/lib/pixelfed`, we might want to back them up, since there's some keys there (and also a lot of `.gitignore` files that I'm excluding here):![image](/attachments/9b9b754b-b273-4403-af4a-0bea45687cca)

image.png

216 KiB

kiara added the

ambition

switch-host

label

2026-06-11 15:44:38 +02:00