[PR #99] [MERGED] Separate difference between backup and export, add a restore-page #118

New issue

Closed

opened 2026-03-02 16:47:47 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 16:47:47 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/photoprism/photoprism-docs/pull/99
Author: @davralin
Created: 1/4/2022
Status: ✅ Merged
Merged: 1/5/2022
Merged by: @graciousgrey

Base: master ← Head: master

📝 Commits (2)

9691d80 Separate difference between backup and export, add a restore-page
960e3f7 Adjustments

📊 Changes

6 files changed (+88 additions, -47 deletions)

View changed files

📝 docs/getting-started/advanced/backups.md (+15 -4)
📝 docs/user-guide/advanced/backups.md (+0 -42)
➕ docs/user-guide/advanced/export.md (+53 -0)
📝 docs/user-guide/advanced/metadata.md (+1 -1)
➕ docs/user-guide/advanced/restore.md (+17 -0)
📝 mkdocs.yml (+2 -0)

📄 Description

As discussed here discussions/772.

I converted default backup-method to just being a sql-dump, and added a docker-compose example.

I also created a dedicated restore-page, that lists all steps needed (including a re-scan).

I also migrated the former "yaml backup" to a dedicated export-document, and adjusted links regarding that there.

I'm not entirely sure what to do with the old user-guide/advanced/backup.md-file - as there's nothing really advanced covered there, everything is either covered in the getting-started/advanced/backup.md, or in user-guide/advanced/export.md instead.

Thoughts?

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/photoprism/photoprism-docs/pull/99 **Author:** [@davralin](https://github.com/davralin) **Created:** 1/4/2022 **Status:** ✅ Merged **Merged:** 1/5/2022 **Merged by:** [@graciousgrey](https://github.com/graciousgrey) **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (2) - [`9691d80`](https://github.com/photoprism/photoprism-docs/commit/9691d80902a4a39b5177734a1b57eeb610e3741a) Separate difference between backup and export, add a restore-page - [`960e3f7`](https://github.com/photoprism/photoprism-docs/commit/960e3f7e63733aaf18231418ac2e8974983c829e) Adjustments ### 📊 Changes **6 files changed** (+88 additions, -47 deletions) <details> <summary>View changed files</summary> 📝 `docs/getting-started/advanced/backups.md` (+15 -4) 📝 `docs/user-guide/advanced/backups.md` (+0 -42) ➕ `docs/user-guide/advanced/export.md` (+53 -0) 📝 `docs/user-guide/advanced/metadata.md` (+1 -1) ➕ `docs/user-guide/advanced/restore.md` (+17 -0) 📝 `mkdocs.yml` (+2 -0) </details> ### 📄 Description As discussed here [discussions/772](https://github.com/photoprism/photoprism/discussions/772). I converted default backup-method to just being a sql-dump, and added a docker-compose example. I also created a dedicated restore-page, that lists all steps needed (including a re-scan). I also migrated the former "yaml backup" to a dedicated export-document, and adjusted links regarding that there. I'm not entirely sure what to do with the old user-guide/advanced/backup.md-file - as there's nothing really advanced covered there, everything is either covered in the getting-started/advanced/backup.md, or in user-guide/advanced/export.md instead. Thoughts? --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>