WeblateOrg / WeblateOrg/docker
Feature: Easy method to add trusted CA Certificate in containerized installation
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 117
- Forks
- 116
- Avg merge
- 1h 21m
- Merged PRs (30d)
- 63
Description
Describe the problem
Your recommendation for handling private CAs is to trust them system-wide. This is a perfectly normal practice for system-wide installations. However, that would require building custom docker images for many on-prem installations, which brings a lot of maintenance overhead.
IMHO this is something that the weblate docker image should support. We certainly do this for our products :)
Describe the solution you'd like
Proposal: A simple environment variable that we could set with a path to a CA certificate.
The entrypoint of the docker image could then add it to the CA bundle itself.
This makes it easy to mount in a CA cert from a volume, as a Kubernetes secret object, etc.
Describe alternatives you've considered
No response
Screenshots
No response
Additional context
No response
Contributor 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.
Research direction
Start by locating the Docker image entrypoint and its existing certificate or trust-store handling. Add support for a configurable CA certificate path that can use a mounted file, then verify the image trusts that certificate when the variable is set.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100