pomerium / pomerium/documentation
Better document Pomerium as standalone solution.
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 13
- Forks
- 23
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 11
Description
Many new Pomerium users begin by setting us up with Traefik or Ingress as the major traffic controller, using us in forward auth mode. Pomerium is a first class proxy and works best independently of competing services.
We want to better highlight that our Proxy service is build on Envoy, why it's production ready, and possibly why it's not a great idea to use us just for forwardAuth.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files or tests; start by reviewing the existing documentation for Pomerium's Proxy service and forward-auth mode. Document the Envoy foundation, production-readiness rationale, standalone use case, and why using Pomerium only for forward auth may be unsuitable.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100