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.

README.md

Documentation

Start with architecture.md — it maps the whole system and links every doc in place. The rest of this page is the same index, grouped by theme, with every doc one click away.

flowchart TB
    A["architecture.md<br/>(the map)"]
    A --> START["Get started"]
    A --> CONCEPTS["Concepts"]
    A --> BUILD["Building apps"]
    A --> OPERATE["Operating"]
    A --> REF["Reference"]

Start here

→ permissions → generative UI → capabilities → surfaces, with a link to the doc for each.

boundaries.

domain, and a first app in ~30 minutes with scripts/install.sh.

enterprise stacks, JS meta-frameworks, and no-code — and the cost of each.

  • analytics.md — first-party, server-side traffic: why a tag

can only see requests that ran JavaScript, how visitors are told apart from bots and from your own operations, and what an honest IP-based count cannot tell you.

Concepts

version, queue, scheduler, and event contracts.

shape, runtime helpers, state/log usage, and response forms.

system tools (ffmpeg, OCR, PDF), the subprocess model, and the trust boundary.

  • realtime.md — the change-log contract: the /ws subscribe

protocol, the signal-only (never-the-body) event, and per-subscriber permission filtering that makes every surface live.

how WebSocket/SSE object events fit.

vs object behavior messages vs realtime streams.

Data, UI, and behavior

forms and views: types, enums, relations, validation bounds, list modes — all enforced on write.

tree/calendar, filters, search, relation labels, forms, and composed detail — no per-app UI code.

flag: comments, attachments, owner-checked sharing, and how to add one.

write, and the business-logic/automation substrate (transitions, notify, triggers, computed, connectors).

goes: the placement flowchart and map, with worked examples (sales tax, payment aging, dunning, refunds) most systems get wrong.

doctrines (stamp vs derive, time belongs to the daemon, money moves, extract-after-repeat, gates vs reactions).

packages, and the stylesheet served as the site_style object at /style.

(detail-vs-edit, the row cap, filters, relation labels, capabilities).

Building & shipping apps

schema+rules+page pattern every app repeats.

semantics, dry-run workflow, and rules for generated packages.

data-preserving upgrade system: baselines, three-way reconcile, overrides, feature flags.

action rules, ownership, row/field filters, sharing, temporary paid access, and audit.

table, {param} patterns, site_404.

vault, hash-only tokens, and the trust boundary.

AI keys, model choice, MCP tool subsets, and building objects by asking.

are operator-installed only, and the trap that follows from it: an object in the override root declares HANDLES and silently never receives one.

through, in order, and which of them can refuse it.

running app without writing server code.

Storage & durability

compaction, and the disposable id→offset sidecar.

and recovery-by-replay.

safe read-only restore preview.

direction for isolating one tenant's data, and what is not decided yet.

Operating

staging with systemd, localhost uvicorn, separate object/data paths.

rate/concurrency/execution boundaries.

  • status.md — readiness checklist, useful deployment shape, and

next production-hardening work.

Reference

clients and tools.

Documentation Rules

  • Keep the root README short enough to explain the project quickly; link into

focused docs from there and from architecture.md.

  • Link docs as a real markdown link, not a ` code span ` — a code span

renders as monospace text and is not clickable on GitHub.

  • Use Mermaid diagrams when they make the system easier to understand.
  • Keep examples safe: no real IPs, private paths, tokens, or deployment names.
  • Prefer runnable examples when the public code supports them.