SYMFONY__ENV__SERVER_NAME appears to be load bearing
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 38/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker
- Domain
- devops, documentation
Research direction
Start by reading the README’s SYMFONY__ENV__SERVER_NAME section and the Docker and reverse-proxy usage described in the issue. Document how to set the variable for normal and reverse-proxy operation with examples, and consider the documentation complete when both access patterns and the variable’s broader effects are clearly explained.
Written by the indexing model from the issue text.
Description
Context
Per the Readme, SYMFONY__ENV__SERVER_NAME functions as a means to specify a user readable 2FA name. However this variable appears to have much larger implications. If malformed, CSS and other app functionality breaks down. In the event that a user is attempting to utilize a reverse proxy to access the app, the value of the variable become critical as simply targeting IP:PORT is not possible.
Request:
Short Term
Additional documentation on the functioning of this variable in the readme, preferably with an added example or two for how to properly set it for normal and behind a reverse proxy operations.
Long Term
A reworking of the app to more gracefully handle calls from different sources (eg: SYMFONY__ENV__SERVER_NAME set to foo.bar.biz renders LAN usage from IP:Port functionally useless due to formatting and other aspects breaking) so that SYMFONY__ENV__SERVER_NAME is no longer mission critical for functionality.
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
koalaman/shellcheck#3593 ·
-
Link Checker ReportOpenautomated issue report
Difficulty 1/5 Under an hour Newbie friendliness 78/100
a2aproject/A2A#2381 ·
Maintainers usually reply within 3 days
-
e2e-failure ready-to-code
Difficulty 1/5 Under an hour Newbie friendliness 82/100
redhat-developer/rhdh-plugin-export-overlays#4485 · 1 comment ·
Maintainers usually reply within 1 day