From 9345907a5c1737c6c2c1f8eba52a568035b08493 Mon Sep 17 00:00:00 2001 From: haturatu Date: Sat, 22 Feb 2025 23:20:55 +0900 Subject: fix: all hange s\/github.com\/ponzu-cms/github.com\/haturatu\/g --- docs/src/Running-Backups/Backups.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/src/Running-Backups') diff --git a/docs/src/Running-Backups/Backups.md b/docs/src/Running-Backups/Backups.md index fde0cab..c2a6989 100644 --- a/docs/src/Running-Backups/Backups.md +++ b/docs/src/Running-Backups/Backups.md @@ -5,7 +5,7 @@ Both the databases `system.db` & `analytics.db`, and the `/uploads` directory ca All backups are made using a `GET` request to the `/admin/backup` path with a query parameter of `?source={system,analytics,uploads}` (only one source can be included in the URL). Here are some full backup scripts to use or modify to fit your needs: -[https://github.com/ponzu-cms/backup-scripts](https://github.com/ponzu-cms/backup-scripts) +[https://github.com/haturatu/backup-scripts](https://github.com/haturatu/backup-scripts) ## System & Analytics The `system.db` & `analytics.db` data files are sent uncompressed in their original form as they exist on your server. No temporary copy is stored on the origin server, and it is possible that the backup could fail so checking for successful backups is recommended. See https://github.com/boltdb/bolt#database-backups for more information about how BoltDB handles HTTP backups. -- cgit v1.2.3