sillsdev / sillsdev/appbuilder-buildengine-api
Make container app server notifications resilient
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- shell, typescript
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100