Add environment variable to handle HTTPS properly
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Read the documented FORCE_HTTPS setting and the linked docker-entrypoint.sh script to understand how the container currently loads its .env configuration. Check how the entrypoint could accept an environment variable and apply it to that setting; done means HTTPS behavior can be configured through the container environment without manually editing persistent storage. The issue has no comments or named tests, so confirm the expected variable behavior before changing files.
Written by the indexing model from the issue text.
Description
Hello !
I'm currently trying to install LinkStack as a pod on my k3s server and i think i'm experimenting an issue with the http / https in the container : i've got 404 errors because sometimes i've got http or https requests in my browser.
I think it might be linked to the var we need to enable in the .env file and referenced in the documentation :
https://docs.linkstack.org/docker/reverse-proxies/#traefik
Start your Docker Compose and navigate to your "persistent storage" and change the .env search for FORCE_HTTPS=false (line 85) and set this to "true"
I think a better way to handle this part light be to add an environnement var in the entry point script, and a sed or similar command to use it in the following script :
https://github.com/LinkStackOrg/linkstack-docker/blob/main/docker-entrypoint.sh
What do you think ? I can try it if you want. 😊
- Dominant language
- Shell
- Stars
- 527
- Forks
- 72
- 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 LinkStackOrg/linkstack-docker
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LinkStackOrg/linkstack-docker#170 · 17 comments · 11 reactions ·
-
Potential information disclosure: runtime Laravel log accessible without authentication in a Docker deploymentPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
LinkStackOrg/linkstack-docker#168 ·
-
Volume path overlap with existing paths inside imagePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 1-2 days Newbie friendliness 52/100
LinkStackOrg/linkstack-docker#162 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 57/100
LinkStackOrg/linkstack-docker#161 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
LinkStackOrg/linkstack-docker#160 · 3 comments ·
All issues in LinkStackOrg/linkstack-docker
Similar issues
-
source:reader type:enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
stephrobert/blog-roadmap#115 ·
-
Python Volcengine provider returns failures instead of raising themPossibly taken @Ricardo-M-L claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
agent-infra/sandbox#248 ·
-
chore priority:low size:S
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
celo-org/celopedia-skills#98 ·
Maintainers usually reply within 1 day
-
Git for Windows shouldn't be locked on their `.windows.1` versionsPossibly taken A pull request linked to this issue is open or already merged. Opengit windows
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jenkins-infra/packer-images#3179 ·
Maintainers usually reply within 1 day
-
ready-for-pr
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kunchenguid/firstmate#7679 · 1 comment ·
Maintainers usually reply within 1 day