Github Deployment Hook - Custom Address/Port w/Secret
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
I do not want the dokploy instance to be accessible from outside connections. Although, I need github to be able to send deployment events and it's not possible to whitelist all the IP addresses of github.
Describe the solution you'd like
It would be nice to be able to define a public address/port specifically for github deployment hooks with or without a secret.
Describe alternatives you've considered
Could have a proxy relay setup but still not ideal.
Contributor guide
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, tests, or entry points. Start by locating the GitHub deployment hook handling and its configuration path. Done means supporting a dedicated public address and port for GitHub deployment events, with optional secret protection, while keeping the Dokploy instance inaccessible from outside connections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100