nextcloud / nextcloud/nextcloud-docker-dev
Trust mkcert CA in containers
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- PHP
- Stars
- 190
- Forks
- 103
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 1
Description
For debugging federation, it would be nice to trust the mkcert CA also in the containers.
- Get the ca path: mkcert -CAROOT
- Copy the root ca to our work directory
- Mount rootCA.pem to /usr/local/share/ca-certificates/rootCA.crt
- Run update-ca-certificates as root
Leaving it here as an idea.
I trusted the certificates manually for now.
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
No file or test is named; start by locating the repository's docker-compose container configuration and inspect how development certificates are mounted. Check mkcert -CAROOT, copy rootCA.pem into the work directory, mount it at /usr/local/share/ca-certificates/rootCA.crt, and run update-ca-certificates as root. Done means federation debugging containers trust the mkcert CA.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100