[PR #158] [MERGED] Kubernetes: Update instructions to properly mount the storage path #166

New issue

Closed

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

kerem commented

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

Owner

📋 Pull Request Information

Original PR: https://github.com/photoprism/photoprism-docs/pull/158
Author: @cjlarose
Created: 6/12/2023
Status: ✅ Merged
Merged: 6/13/2023
Merged by: @lastzero

Base: master ← Head: patch-1

📝 Commits (2)

f54a3a8 Update kubernetes instructions to use default paths
c712927 Use separate kubernetes volumes for originals and import dirs

📊 Changes

1 file changed (+14 additions, -20 deletions)

View changed files

📝 docs/getting-started/advanced/kubernetes.md (+14 -20)

📄 Description

The kubernetes instructions had a few issues. Namely,

PHOTOPRISM_EXPORT_PATH was being set, but this doesn't seem to have any effect (or at least this env var isn't documented anywhere else)
PHOTOPRISM_STORAGE_PATH was not explicitly set, so it would default to /photoprism/storage, which would be in ephemeral storage (since that directory was not declared as a volume)
PHOTOPRISM_BACKUP_PATH was similarly not set, so the directory would have been ephemeral.

In my experience, these problems (especially the unset PHOTOPRISM_STORAGE_PATH var) caused issues since it meant that photoprism was unable to store API keys on boot, preventing the activation of a membership.

_{🔄 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/158 **Author:** [@cjlarose](https://github.com/cjlarose) **Created:** 6/12/2023 **Status:** ✅ Merged **Merged:** 6/13/2023 **Merged by:** [@lastzero](https://github.com/lastzero) **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (2) - [`f54a3a8`](https://github.com/photoprism/photoprism-docs/commit/f54a3a805286e4909712a360d9daa176f2ecfef1) Update kubernetes instructions to use default paths - [`c712927`](https://github.com/photoprism/photoprism-docs/commit/c71292773047690c3c4299496a5f572aeb6e0772) Use separate kubernetes volumes for originals and import dirs ### 📊 Changes **1 file changed** (+14 additions, -20 deletions) <details> <summary>View changed files</summary> 📝 `docs/getting-started/advanced/kubernetes.md` (+14 -20) </details> ### 📄 Description The kubernetes instructions had a few issues. Namely, * `PHOTOPRISM_EXPORT_PATH` was being set, but this doesn't seem to have any effect (or at least this env var isn't documented anywhere else) * `PHOTOPRISM_STORAGE_PATH` was not explicitly set, so it would default to `/photoprism/storage`, which would be in ephemeral storage (since that directory was not declared as a volume) * `PHOTOPRISM_BACKUP_PATH` was similarly not set, so the directory would have been ephemeral. In my experience, these problems (especially the unset `PHOTOPRISM_STORAGE_PATH` var) caused issues since it meant that photoprism was unable to store API keys on boot, preventing the activation of a membership. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>