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
rules.json · 2.2 KB · 25 lines
1{
2 "rules": [
3 {
4 "effect": "allow",
5 "principal": "public",
6 "actions": ["execute"],
7 "object_id": "site_notary",
8 "reason": "an attestation only its submitter can look up is not an attestation, it is a favour -- the entire value of lodging a digest with an independent party is that a third person (a customer, an auditor, the other side of an argument) can check it without an account here, a relationship with the operator, or anybody's permission. The page reads nothing keyed to a person and returns nothing but a hex string, a timestamp and the submitter's own chosen label"
9 },
10 {
11 "effect": "allow",
12 "principal": "public",
13 "actions": ["execute"],
14 "object_id": "action_notarize",
15 "reason": "PUBLIC on the object, GATED IN THE OBJECT: action_notarize refuses an anonymous submission with a 409 naming notary.public_submission unless the operator has set it. The gate lives in the code rather than here because the two deployments are one setting apart -- a notary run as a service for other people must accept strangers, a notary run for one business's own ledger heads must not -- and an operator should not have to edit permission rules to change which one they are running. Accepting a digest is close to the safest write on this box in any case: it stores 64 hex characters, learns nothing about the submitter, and cannot overwrite or move an existing record"
16 },
17 {
18 "effect": "allow",
19 "principal": "registered",
20 "actions": ["read"],
21 "collection": "notarizations",
22 "reason": "READ ONLY, and read only is the entire product. No update and no delete are granted here because a notary with an edit path is a notary whose operator can be leaned on, and every claim anybody makes from this log rests on there being no way to amend it after the fact. No create either: action_notarize is the one writer, because a row typed by hand is a timestamp somebody chose rather than one the server observed, and the object is also what enforces that resubmitting returns the ORIGINAL record instead of a later one. The collection is append storage besides, so there is no update or delete to grant even if somebody wanted to"
23 }
24 ]
25}