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 · 2.3 KB · 38 lines
1{
2 "id": "app-materialize",
3 "name": "Materialize",
4 "version": "0.2.0",
5 "description": "Declarative generation jobs that CREATE new records (plan/vocabulary/61-materialize-spec.md), the write-side sibling of app-rollup's read-side aggregation. materialize_definitions (admin-owned) declares a source + filter + trigger (scheduled/scheduled_fixed/event) + output collection (optionally with children) + idempotency_key + mapping; the daemon's materialize pass (object_daemon.process_materializations, object_materialize.py) generates due output through the target collection's own existing create/update path, with a crash-safe children-first-header-last write order and an integer-cents balance check enforced before any write. Covers three shaped-alike gaps found by the parity audit: recurring journals, depreciation, and template-execution/CreateWork. system_materialize_run is a manual 'Run now' escape hatch (and, in v1, the way event-mode definitions run at all -- see next); system_materialize_seed is the event-mode (CreateWork) dispatch handler, shipped inert (HANDLES == []): the platform deliberately does NOT rewrite an installed object's source at runtime to track the definition set, so automatic on-create dispatch is off in v1 and event-mode degrades to the manual path. The dispatch logic is built and tested, ready for a future deliberate/scheduled HANDLES-sync job. No dedicated authoring page in v1 -- materialize_definitions already gets a generated admin form (docs/schema-forms.md). Target collections are NOT declared here: each is an existing, already-schema'd collection the requesting app already owns.",
6 "compatibility": {
7 "dbbasic_object_server": ">=0.1.0"
8 },
9 "dependencies": [],
10 "objects": [
11 {
12 "id": "system_materialize_run",
13 "path": "objects/system/materialize_run.py"
14 },
15 {
16 "id": "system_materialize_seed",
17 "path": "objects/system/materialize_seed.py"
18 },
19 {
20 "id": "site_materialize_run_button",
21 "path": "objects/site/materialize_run_button.py"
22 }
23 ],
24 "schemas": [
25 {
26 "collection": "materialize_definitions",
27 "path": "schemas/materialize_definitions.json"
28 }
29 ],
30 "permissions": [
31 {
32 "path": "permissions/rules.json"
33 }
34 ],
35 "seed": [],
36 "migrations": [],
37 "nav_optional": true
38}