Thread with 1 post
jump to expanded post
I created a small backup helper for my #gotosocial instance:
gitea.zlatko.dev/zlatko/gts-backup
I can use it directly with npm (you probably shouldn't, it's not very well tested):
npx gts-backup -p @zladuric/gts-backup -s /mnt/my-instance -d /mny/backup -u zlatko and it will copy the database, and all the media uploaded by me to the backup location.
In theory (and practice, as I've just tested), you can make that copy, point your GTS data volume to the new location, and things just keep working.
(#npm package here: www.npmjs.com/package/@zladuric/gts-backup)
Warning: unsafe, untested plus zero tests, and I have no idea if I'll ever write more code there. But maybe it'll inspire a proper backup tool somewhere down the line.
The problem I tried to solve with just regular GTS backup is you pull a lot of remote media, so backup of all that (unless you're running a "super serious" server) makes no sense and is exensive.
In light of social.zlatko.dev/@zlatko/statuses/01GJAMRC6AH9JS4F9VZFPF3GW5, I'm sorry, y'all :)
CC @gotosocial