[Feature Request] add unique cookie prefix or allow setting
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker
- Domain
- infrastructure
Research direction
No file, test, or entry point is identified in the issue. Start by tracing how the Docker setup passes configuration to wallabag and how wallabag names the REMEMBERME and PHPSESSID cookies; done means separate containers no longer overwrite each other's session cookies, with the requested prefix or configuration option documented.
Written by the indexing model from the issue text.
Description
Hello,
I am running this along with a few dozen other containers on a small home server with podman under one IP (using different port numbers for each service). It works pretty well aside from one issue: session cookie names often conflict causing frequent log outs.
wallabag uses generic names "REMEMBERME" and to a lesser extent "PHPSESSID". Would it be possible to append a unique prefix to the session ID cookie name (ie: 'wallabag_REMEMBERME') or allow us to add a prefix using an environment variable?
Thank you :)
- Dominant language
- Shell
- Stars
- 771
- Forks
- 168
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wallabag/docker
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 57/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Awaiting response
Difficulty 4/5 3-5 days Newbie friendliness 32/100
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
Similar issues
-
roadmap-100
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
priority: medium status: needs-decision work-class: scoped
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
melodic-software/claude-code-plugins#9339 · 2 comments ·
Maintainers usually reply within 1 day
-
数据界面的横向滚动条缺失Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
zilliztech/attu#1037 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
community-scripts/ProxmoxVE#18073 · 1 comment ·
Maintainers usually reply within 1 day
-
Uptime "Test Monitor" always fails with an empty HTTP 400 (uptime-checker API endpoint not configured)Possibly taken @ayoubjemai claimed this today. OpenWaiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
getsentry/self-hosted#4582 ·
Maintainers usually reply within 1 day