Runs live, versioned Python application objects on one VM, with a suite of apps: projects, notes, tasks, files and more.

0 downloads

Download zip
Clone
Clone with git
git clone https://gitstable.com/git/askrobots/dbbasic-object-server.git
HTTPS
https://gitstable.com/git/askrobots/dbbasic-object-server.git
SSH
ssh://git@gitstable.com:2222/askrobots/dbbasic-object-server.git

Cloning needs no sign-in. Pushing over HTTPS asks for your username and an access token. SSH needs your key under SSH keys.

danq9 signup: the person chooses the password and name on the confirm page 83c7aa6 2 weeks, 5 days ago History
dbbasic-package.json · 1.4 KB · 13 lines
1{
2 "id": "app-notify",
3 "name": "Notify",
4 "version": "0.1.0",
5 "description": "Declarative notifications (plan/vocabulary/12-notify-spec.md): a notify_rules row turns a record-change event into notifications, replacing the bespoke 'email me when X happens' object every app grows. The daemon's process_notifications pass polls the record-change log (object_notify), matches enabled rules (event_pattern + flat match, restricted to CHANGED fields on updates), resolves recipients (owner/field/users/role, suppressing the actor by default), renders the body_template, and appends a notifications row per recipient -- surfaced by the nav bell + realtime, unmodified. Polling the change log (not synchronous HANDLES dispatch) means it works with no event-handler dependency, at-least-once. v1 delivers the in_app channel; email waits on 01-email-adapter (recognized + skipped), digest batching too. Ships one example rule (task assigned -> notify the assignee). admin-owned rules. notify_enabled kill switch.",
6 "compatibility": { "dbbasic_object_server": ">=0.1.0" },
7 "dependencies": ["app-tasks", "app-collab"],
8 "objects": [],
9 "schemas": [ { "collection": "notify_rules", "path": "schemas/notify_rules.json" } ],
10 "permissions": [ { "path": "permissions/rules.json" } ],
11 "seed": [ { "collection": "notify_rules", "path": "seed/notify_rules.tsv" } ],
12 "migrations": []
13}