Consider Traefik or similar for HTTPS etc. (milestone E)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
As discussed in Mexico.
The use case is having Dataverse on a server that you want to show to a non-technical audience. That audience shouldn't have to worry about SSL certs or being on weird ports like 8080.
It doesn't have to be Traefik. It could be nginx or similar.
Do we want to use certbot from Let's Encrypt by default? Or let people bring their own cert.
Related topic in Zulip: https://dataverse.zulipchat.com/#narrow/channel/375812-containers/topic/add.20Traefik/near/434714994
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 files, tests, or entry points are named. Start by reviewing the related Zulip discussion and comparing the Traefik, nginx, and certificate-management options. Done means a decided approach supports HTTPS on standard ports and clearly defines whether certificates come from Let's Encrypt or the user.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100