Make container app server notifications resilient

Open
#87 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
shell, typescript
Domain
backend, devops

Research direction

Start with publish.sh to trace how notifications are sent to ScriptureEarth and container-app-servers, then follow the BuildEngine entry point that could own retry behavior. Define the enqueue and retry flow for an unavailable server, and verify that a notification is eventually re-sent after the server becomes available.

Written by the indexing model from the issue text.

Description

publish.sh is sending notifications to ScriptureEarth (and soon independent container-app-servers) and will not be re-sent if the server is not available. We should have a way for publish.sh to enqueue the notification and have BuildEngine retry if necessary.

Dominant language
TypeScript
Stars
1
Forks
2
No merged PRs in 30d

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.

More from sillsdev/appbuilder-buildengine-api

All issues in sillsdev/appbuilder-buildengine-api

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.