Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should wiki pages be represented as git commits or database records? #1

Open
jdmarshall opened this issue May 4, 2024 · 0 comments

Comments

@jdmarshall
Copy link
Member

Keeping a split source of truth or system of record would be very awkward.

One of the notable problems I encountered with Trac was that there was no AST that represented a page, so for instance identifying the hyperlinks was something that needed to be done fresh on each load, and then repeated by any plugins. So none of the plugins supported every form of link and wiki word allowed.

So from this standpoint storing the DOM into a database for later perusal would be better. It also provides a way to handle page renames, since move operations could link to a page ID determined when the link was created.

Or it could be split. Every commit has a hash, and we could build or rebuild state from that if it is missing.

Either way we still need to be able to read and scan code commits anyway, so we won’t completely avoid git integration.

But reading for would make bootstrapping a bit easier. All things to consider.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant