mirror of
https://github.com/narrrl/narl-workspace.git
synced 2026-11-03 16:41:27 +01:00
nvrl
49b2056215
The diary grows into a workspace: a flat list of dated entries becomes a tree of spaces, and the app is renamed to match what it now is. Spaces and nodes One recursive `nodes` table replaces `entries`: a space is a root node, and folders and documents nest under it without limit. Entries keep their ids through the migration, so share tokens, media links and the drafts in localStorage all still resolve. Folder import A folder or a zip is uploaded as a document tree. Markdown becomes documents titled from their first heading, everything else becomes media, and relative links between the imported files are rewritten to the paths they landed at, so a set of cross-linked notes stays navigable after the upload. Boards A kanban board per space, with the space as the board: lists, cards, due dates and an optional link to a document. `diary` has none. Mail SMTP notifications through an outbox. A mail is enqueued under a key naming the occurrence it belongs to, so a restart cannot resend and a relay that refuses is retried with a widening backoff. Four kinds: the diary reminder, cards due and overdue, a weekly digest, and logins from a browser that has not been seen before or a burst of failures. All of it is dormant until WORKSPACE_SMTP_URL is set. Rename Everything user-visible says workspace; everything that already exists outside this repo keeps its name, because renaming it would break a running deployment for tidiness alone: the database file, the docker volume, the session cookie, the Proton device, the keyring entry and the localStorage keys. Configuration reads WORKSPACE_* first and falls back to DIARY_*, so the deployed .env keeps working untouched.
46 lines
1.9 KiB
SQL
46 lines
1.9 KiB
SQL
-- A board per space, so "what am I working on" can be asked per space instead
|
|
-- of across everything at once. There is no board table: a space *is* its
|
|
-- board, and `nodes.has_board` decides whether the view exists. The diary is a
|
|
-- journal rather than a project and keeps that flag off.
|
|
|
|
CREATE TABLE board_lists (
|
|
id INTEGER PRIMARY KEY AUTOINCREMENT,
|
|
-- A space. Dropping the space drops its board with it.
|
|
space_id INTEGER NOT NULL REFERENCES nodes (id) ON DELETE CASCADE,
|
|
name TEXT NOT NULL,
|
|
position INTEGER NOT NULL,
|
|
created_at INTEGER NOT NULL
|
|
);
|
|
|
|
CREATE INDEX idx_board_lists_space ON board_lists (space_id, position);
|
|
|
|
CREATE TABLE cards (
|
|
id INTEGER PRIMARY KEY AUTOINCREMENT,
|
|
list_id INTEGER NOT NULL REFERENCES board_lists (id) ON DELETE CASCADE,
|
|
-- The document this card is about, if any. Deleting that document must not
|
|
-- delete the card: the work is still open, only its notes are gone.
|
|
node_id INTEGER REFERENCES nodes (id) ON DELETE SET NULL,
|
|
title TEXT NOT NULL,
|
|
body TEXT NOT NULL DEFAULT '',
|
|
due_at INTEGER,
|
|
done_at INTEGER,
|
|
position INTEGER NOT NULL,
|
|
created_at INTEGER NOT NULL,
|
|
updated_at INTEGER NOT NULL
|
|
);
|
|
|
|
CREATE INDEX idx_cards_list ON cards (list_id, position);
|
|
CREATE INDEX idx_cards_node ON cards (node_id);
|
|
-- The reminder mails in the next phase ask "what is due", which is a question
|
|
-- about every board at once.
|
|
CREATE INDEX idx_cards_due ON cards (due_at) WHERE due_at IS NOT NULL AND done_at IS NULL;
|
|
|
|
-- The three columns every board starts with, for the spaces that already exist.
|
|
INSERT INTO board_lists (space_id, name, position, created_at)
|
|
SELECT n.id, l.name, l.position, strftime('%s', 'now')
|
|
FROM nodes n
|
|
CROSS JOIN (SELECT 'backlog' AS name, 0 AS position
|
|
UNION ALL SELECT 'doing', 1
|
|
UNION ALL SELECT 'done', 2) l
|
|
WHERE n.parent_id IS NULL AND n.kind = 'space' AND n.has_board <> 0;
|