Tripletex / Tripletex/tripletex-api2

Best way to sync projects?

Open
#62 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
49
Forks
47
Avg merge
1h 1m
Merged PRs (30d)
1

Description

Is there any good practice to sync tripletex projects to on-prem database?
We have a customer that needs a local db with tripletex projects and we want to keep the sync job to minimum data transfer.
The customer service has a "changedSince" property that works perfect. Is there anything similar to projects?

Contributor guide

No contributing guide indexed for this repository

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

The issue names no file, test, or entry point. Start by reviewing the project and customer-service API documentation, then check how project changes are represented for synchronization. Done means the supported incremental-sync behavior and its data-transfer implications are clearly documented.

Written by the indexing model from the issue text.

Assessment

Domain
api, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.