Skip to content

Using database instead of files and directories #1406

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

Closed
sircode opened this issue Oct 28, 2024 · 1 comment
Closed

Using database instead of files and directories #1406

sircode opened this issue Oct 28, 2024 · 1 comment

Comments

@sircode
Copy link

sircode commented Oct 28, 2024

Is there a reason you are working with files for title and content and directories as "categories" and not simply a database?

@stefan-niedermann
Copy link
Member

It is a tradeoff that has been discussed way more than once here.

Long story short: A file system avoids vendor lock in, avoids proprietary formats, allows the easiest possible export, requires absolutely no knowledge, ot works with the default Nextcloud desktop sync clients, it ensures interoperability with nearly each editor the user prefers without requiring to implement a specific API or format and a few others.

Drawbacks can be performance (if done wrong), missing features like tags (which may be achieved using frontmatter).

As a blocker for #299 there has been mich discussion there.

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

No branches or pull requests

3 participants