Dokploy / Dokploy/dokploy

Generic Git repo: calls to webhook require headers and payload

Open
#633 8 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

To Reproduce
  1. Deploy an app from a Git repository source (I used a repo on Azure DevOps and a matching SSH key to deploy manually, which worked fine)
  2. Copy webhook url
  3. Call webhook url from a browser (GET) or using Postman (POST)
Current vs. Expected behavior

Current: "branch not match"

Expected: deploy app with it's settings from Dokploy (i.e. configured branch and last commit) as generic Git repository providers don't send any payload, or not a payload that Dokploy can interpret

Provide environment information
Operating System: Ubuntu 24.04.1 LTS
Dokploy: 0.10.4
VPS Provider: Azure
App: Dotnet backend+Svelte frontend using a custom Dockerfile which is in the repo root
Which area(s) are affected? (Select all that apply)

Application

Additional context

If I pass a fake "X-Event-Key" header and fake JSON body along with the request, it works:

X-Event-Key: repo:push

{ 
    "push" : {
        "changes" : [
            { 
                "new" : { "name" : "master", "target" : { "message" : "Auto deploy", "hash" : "NEW_COMMIT" } }
            }
        ]
    }
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the webhook URL handling for applications deployed from a generic Git repository, and reproduce GET and POST requests with and without the X-Event-Key header and payload shown in the issue. Done means a valid webhook triggers deployment using the app's configured branch and last commit without requiring provider-specific headers or payload data.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.