Skip to content

Playing around with yaml#27

Draft
amnuts wants to merge 2 commits into
developfrom
yaml-files
Draft

Playing around with yaml#27
amnuts wants to merge 2 commits into
developfrom
yaml-files

Conversation

@amnuts
Copy link
Copy Markdown
Owner

@amnuts amnuts commented May 9, 2026

Looking into using yaml for come of the config files - config, rooms, and command help docs.

Could be a pre-cursor to having the users as a single yaml file per user (user details, mail, reminders, macros, etc.)

Did consider SQLite as well and having everything in there, but this seemed an easier route that people could still easily update without having to go through anything but a text editor.

@amnuts amnuts changed the base branch from main to develop May 9, 2026 20:41
@Uzume
Copy link
Copy Markdown

Uzume commented May 13, 2026

I question the value of putting things like mail and/or chat logs into the same file as user setting data, etc. That said, a standard text format like YAML is probably a good idea.

@amnuts
Copy link
Copy Markdown
Owner Author

amnuts commented May 13, 2026

@Uzume, I was thinking that direction just to have a single user file that's all self-contained - no more multiple-directories to read from for one user. What's your concern about having a user's related content in a file a single file for that user?

Agreed about yaml, and seemed to fit better in this context than json/jsonl. And would certainly make it much easier to add new properties to the user object than the specific structure it has now!

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

Successfully merging this pull request may close these issues.

2 participants