Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Bring back self-signed cert docs and expand with reverse-proxy note #11520

Merged
merged 3 commits into from
Oct 8, 2024

Conversation

ryan953
Copy link
Member

@ryan953 ryan953 commented Oct 8, 2024

This brings back the self-signed cert notes from #11491 that @evanpurkhiser originally wrote. It wasn't working on it's own, but with a reverse proxy in front it is solving a problem I had.

Depends on getsentry/sentry#78774

Copy link

vercel bot commented Oct 8, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
changelog ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 8, 2024 7:09pm
develop-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 8, 2024 7:09pm
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
sentry-docs ⬜️ Ignored (Inspect) Visit Preview Oct 8, 2024 7:09pm

@joshuarli joshuarli merged commit 0c9542f into master Oct 8, 2024
9 checks passed
@joshuarli joshuarli deleted the ryan953/https-proxy branch October 8, 2024 19:35
ryan953 added a commit to getsentry/sentry that referenced this pull request Oct 8, 2024
This creates a new command `yarn https-proxy` to help people use their
dev servers over https.


The json file content was generated using `caddy adapt` with this config
as input:
```
:8003
reverse_proxy localhost:8000
tls ./config/localhost.pem ./config/localhost-key.pem
```

Relates to getsentry/sentry-docs#11520
@github-actions github-actions bot locked and limited conversation to collaborators Oct 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants