[PR #437] [MERGED] docs/example/docker: Add COOKIE_PATH example to compose #27327

Closed
opened 2026-06-20 10:35:47 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/imputnet/cobalt/pull/437
Author: @MiraiSubject
Created: 4/17/2024
Status: Merged
Merged: 4/19/2024
Merged by: @wukko

Base: currentHead: add-cookie-path-docs


📝 Commits (1)

  • 009f4ac docs/example/docker: COOKIE_PATH example to compose

📊 Changes

1 file changed (+2 additions, -0 deletions)

View changed files

📝 docs/examples/docker-compose.example.yml (+2 -0)

📄 Description

To prevent other people like me: https://github.com/wukko/cobalt/issues/435 from running into this if they rush into deploying the compose file.

imo a COOKIE_PATH example should also be included in the compose file if a volume suggestion for it is offered, or alternatively, in the app try to read COOKIE_PATH and if it doesn't exist read /cookies.json. I didn't read the table at the bottom under the docker compose section and I actually found this out from cloning the source code and searching for cookie lol


🔄 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/imputnet/cobalt/pull/437 **Author:** [@MiraiSubject](https://github.com/MiraiSubject) **Created:** 4/17/2024 **Status:** ✅ Merged **Merged:** 4/19/2024 **Merged by:** [@wukko](https://github.com/wukko) **Base:** `current` ← **Head:** `add-cookie-path-docs` --- ### 📝 Commits (1) - [`009f4ac`](https://github.com/imputnet/cobalt/commit/009f4acbb3080f2b8c6991967f7a86967b2882c9) docs/example/docker: COOKIE_PATH example to compose ### 📊 Changes **1 file changed** (+2 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/examples/docker-compose.example.yml` (+2 -0) </details> ### 📄 Description To prevent other people like me: https://github.com/wukko/cobalt/issues/435 from running into this if they rush into deploying the compose file. > imo a COOKIE_PATH example should also be included in the compose file if a volume suggestion for it is offered, or alternatively, in the app try to read COOKIE_PATH and if it doesn't exist read /cookies.json. I didn't read the table at the bottom under the docker compose section and I actually found this out from cloning the source code and searching for cookie lol --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-06-20 10:35:47 -05:00
Sign in to join this conversation.