Use Mergin webhooks

Open
#6 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api, backend

Research direction

Start by tracing the existing regular polling path for Mergin project changes and identify where an optional webhook listener would connect. The work is done when new data pushed to a project can be received through Mergin webhooks without removing the polling option.

Written by the indexing model from the issue text.

Description

enhancement

Currently we poll Mergin in regular intervals to see if there are any changes to the project. Optionally there should be a way to listen to Mergin webhooks in case there are new data pushed to the project.

Dominant language
Python
Stars
53
Forks
24
No merged PRs in 30d

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.

More from MerginMaps/db-sync

All issues in MerginMaps/db-sync

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.