!toke commands stored in DB document (default tokes.json checked/loaded into DB at boot) #24

Closed
opened 2024-11-15 18:13:59 -05:00 by rainbownapkin · 5 comments
rainbownapkin commented 2024-11-15 18:13:59 -05:00 (Migrated from gitlab.com)
No description provided.
rainbownapkin commented 2024-11-15 18:13:59 -05:00 (Migrated from gitlab.com)

added #23 as parent issue

added #23 as parent issue
rainbownapkin commented 2024-11-15 18:14:30 -05:00 (Migrated from gitlab.com)

changed title from !toke commands stored in DB document (default tokes.json loaded at boot) to !toke commands stored in DB document (default tokes.json {+checked/+}loaded at boot)

changed title from **!toke commands stored in DB document (default tokes.json loaded at boot)** to **!toke commands stored in DB document (default tokes.json {+checked/+}loaded at boot)**
rainbownapkin commented 2024-11-15 18:14:30 -05:00 (Migrated from gitlab.com)

changed the description

changed the description
rainbownapkin commented 2024-11-15 18:14:36 -05:00 (Migrated from gitlab.com)

changed title from !toke commands stored in DB document (default tokes.json checked/loaded at boot) to !toke commands stored in DB document (default tokes.json checked/loaded {+into DB +}at boot)

changed title from **!toke commands stored in DB document (default tokes.json checked/loaded at boot)** to **!toke commands stored in DB document (default tokes.json checked/loaded {+into DB +}at boot)**
rainbownapkin (Migrated from gitlab.com) closed this issue 2024-12-10 22:31:04 -05:00
rainbownapkin commented 2024-12-10 22:31:05 -05:00 (Migrated from gitlab.com)

Added !toke command DB schema, default toke command autoloading logic, and live command cache to prevent constant database access from '!toke' calls: d516fed309

Added !toke command DB schema, default toke command autoloading logic, and live command cache to prevent constant database access from '!toke' calls: d516fed3092c7eeefdbee0cee7cc0e9e60c7622b
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: rainbownapkin/canopy#24
No description provided.