Projects, Roster and Inbox: sync tasks, runs and the Inbox from every connected Muster Server at once

Open
  • Is something wrong?
#806 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
electron, typescript
Domain
desktop

Research direction

Start from runtime/domains/paperclip.ts, where the single-server sync pipeline (OrgReader, live socket, writes) lives. Read #803 and spec clause 13 to learn the current connection model. Write workflow tests for two-server sync first (red), then merge one reader per server into a tagged snapshot. Done when acceptance criteria 1-4 pass: both servers' rows show labelled and writes route to source.

Written by the indexing model from the issue text.

Description

type:feature

Follow-up to #803 (part of #146 / #147).

After #803, Settings › Integrations holds many Muster Servers side by side. Projects and orgs are read from every connected server at once and labelled with their server. Tasks-as-chats, Roster, Inbox, Ledger, runs, routines, approvals and the live socket still sync from one server at a time: the one marked "Projects, Roster and Inbox sync from this server" in the list, changed with Use for Projects.

That sync is one pipeline in runtime/domains/paperclip.ts: one backend, one org read (built), one live socket and session, one write path, and orgs.*/check-out on that connection. Merging it across servers means:

  • one OrgReader and live socket per connected server, merged into one snapshot with every row tagged by server;
  • writes (comment, status, assign, approve, cancel run, Work locally) routed to the server the row came from;
  • the Inbox and badge counting items from every server;
  • approvals carried over by an import decidable on the server they came from, not only the synced one (linkedApproval);
  • a browser-session cookie for a server that is not the synced one kept for that server (today it waits on the synced connection).

Acceptance (spec clause 13, workflow tests red first):

  1. With two servers connected, tasks, agents, runs and Inbox items from both show at once, each labelled with its server.
  2. Acting on a row writes only to its own server.
  3. One server going offline shows its rows as offline and leaves the other's live.
  4. No "Use for Projects" choice is needed any more; it is removed.
Dominant language
TypeScript
Stars
3
Forks
0
Avg merge
17h 33m
Merged PRs (30d)
163

Getting set up

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 musterhq/muster-code

All issues in musterhq/muster-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.