Proxy Advice
- Dominant language
- C#
- Stars
- 5.1k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Managed to get everything up and running, i use apache for reverse proxy but followed the advice here and used caddy, which ended up causing quite a bit of drama for me for nearly everything else i host behind that reverse proxy.
Caddy2 doesn't seem fully documented yet - it has documentation but its really lightweight and doesn't cover a whole host of eventualities. After a lot of tweaking i got most things working but had such issues with wordpress i had to switch back to apache.
I put remotely through apache2 and so far can find no issue. Is there something specific that doesnt work with anything but caddy?
Just trying to work out why this advice exists and if it isn't actually quite misleading?
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue refers to the reverse-proxy advice and compares Caddy2 with Apache2, but it names no documentation file, test, or entry point. Review the current Caddy guidance and verify whether Remotely has any Caddy-specific requirements; done means the documentation clearly explains the supported proxy options and why Caddy is recommended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache, wordpress
- Domain
- documentation, infrastructure, networking
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100