prometheus-community / prometheus-community/PushProx
how about pushprox-proxy service over https?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 811
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
great job, this project does exactly what we need when the clients are unreachable. imagine that your clients are different companies and therefore no VPN or shenanigan like that is authorized. Client must push.
is this project still maintained?
will you add https for the pushprox-proxy one day?
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
No files, tests, or entry points are named. Start by reviewing the pushprox-proxy service and its current transport configuration, then clarify the HTTPS requirements and supported deployment constraints. Done should mean an agreed HTTPS approach is implemented and verified, but the issue does not define those acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100