getsentry / getsentry/self-hosted

NGINX automatic SSL

Open
#4,506 4 comments 0 reactions 0 assignees View on GitHub
Waiting for: Product Owner
Dominant language
Shell
Stars
9.6k
Forks
2k
Avg merge
1d 5h
Merged PRs (30d)
15

Description

### Problem Statement

When I setup my self-hosted sentry instances, I have to run a separate webserver (like traefik) and point it to the NGINX service

### Solution Brainstorm

Just like GitLab, We can Embed an ACME resolver (Like goacme/lego or certbot or acme.sh [I would prefer lego since it has a lot of native integrations and it is easier to configure specially if a user wants to get certificate using DNS01]) and handle TLS Termination natively

And by making it configurable, Users are able to Provide their own certificate too

Also by that We can make sentry to ask for user's domain on setup So It will set other configurations that should set while setting up sentry to work with a domain

If it is an accepted thing I Would like to make a PR for that

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by reviewing the self-hosted NGINX service and setup configuration, then clarify the scope for ACME certificates, user-provided certificates, and domain setup. Done would require an agreed design covering TLS termination and the related configuration changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, nginx
Domain
devops, infrastructure, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.