Replies: 3 comments
|
That would be practical and safer: if the database get corrupted your memos are safe. |
Yeah I actually thought this would be the best way to do it actually. Like the attachments storage setting it would be great if the memo content itself could be configured for in database or in filesystem. In the meantime I have made this PR: #5998 I don't really think that's the best way to do it, but it's quick and easy and meets my needs. Not sure if the maintainers want it that way though. |
|
Ok my PR was rejected so I directed claude to make a separate python package that accomplishes what I want using the memos API. I just did this yesterday and I'll keep tinkering with it as I discover issues, but so far it seems to do pretty much exactly what I want. Wish I didn't need to run a separate container for this but oh well. |
Uh oh!
There was an error while loading. Please reload this page.
Is anyone interested in an option to have the server periodically dump the DB content to markdown files? I really just want all of my memos to exist on disk as regular markdown files so there is more of a chance of someone being able to access them if I'm not around. I think keeping the memo content in the database is fine for me, but I'm talking like continuity planning here.
Maybe this feature already exists? I was thinking I could just run a script periodically that connects to the db and does this but then I realized the best place to do it is probably from memos itself. Happy to work on a PR if it's something people want and could get approved.
All reactions