I wrote like the 5th version of wiki software maybe ~2 years ago and I use it ALL THE time.
It's the only bookmark I need. It uses pretty vanilla django, but with Django Tree Queries [0].
Which make a tree structure in SQL. A robust and almost 1st class tree structure. I know it's too complicated, but this works out great for a wiki. I can re-home whole sections by just moving a tree node.
Anywho, why I am excited is I thought it needed Postgres to support
[0]: https://django-tree-queries.readthedocs.io/en/latest/
Paul SomeoneElse /
npub1y2…wel6u
2024-04-01 01:23:25
Author Public Key
npub1y2p02vwdvgzv009rsmv4ze9mv9gg44t95dl2z8dgdvyz5ej2edqqcwel6uPublished at
2024-04-01 01:23:25Event JSON
{
"id": "aa788e518db111eb97125527cf48f6e29adb3e379ddc0de71a91ce50205e5c2d",
"pubkey": "2282f531cd6204c7bca386d95164bb61508ad565a37ea11da86b082a664acb40",
"created_at": 1711934605,
"kind": 1,
"tags": [
[
"proxy",
"https://mastodon.sdf.org/users/pkw/statuses/112193346334218606",
"activitypub"
]
],
"content": "I wrote like the 5th version of wiki software maybe ~2 years ago and I use it ALL THE time.\n\nIt's the only bookmark I need. It uses pretty vanilla django, but with Django Tree Queries [0]. \n\nWhich make a tree structure in SQL. A robust and almost 1st class tree structure. I know it's too complicated, but this works out great for a wiki. I can re-home whole sections by just moving a tree node.\n\nAnywho, why I am excited is I thought it needed Postgres to support\n\n[0]: https://django-tree-queries.readthedocs.io/en/latest/",
"sig": "553174ee36b62cf36ebacebe0efaa1520c78860548e2457552936e5d23aad21b215484e3f62d95bcdb36834ba3dbf73807b1d64fa395550cfb40b8a8dcee1980"
}