datum
datum copied to clipboard
datumforge
Datum's central server
Datum will provide a set of root `jsonschema` templates for documents such as invoices, quotes, etc. These need to be seeded into the database and accessible to all users to...
- Add authorization checks - Ensure regular users cannot create `roottemplates`, these are seeded into the database and owned by the datum system - Add tests
- Add permission checks - Add tests
Example structure: ``` ├── datum_controlled_top_level
To enable development, we currently generate keys on startup if none are provided, instead we should fail to start if no keys are provided when not in dev: https://github.com/datumforge/datum/blob/main/cmd/serve.go#L130-L132
The existing tuple cleanup works when an object is being deleted by ID, however, on cascade deletes where a `predicate` is used, we don't have the object ID and the...
Today the json output works but as we grow in objects it would be convenient to: - have a table row writer for cleaner output - cap the results returned...
By default, a dedicated database is not created per org, but currently controlled by a field in the organization `dedicated_db`. Instead of allowing this to be set directly, this should...
Our current transactional email provider (Sendgrid) is today just blasting emails out via API requests - given we have the user context when sending the email, we should start tracking...