Make config updates-compatible #12

Closed
opened 2023-03-15 22:47:10 +02:00 by profitroll · 0 comments
Owner

File config.json should be replaced by config_example.json or something like that, and admin needs to copy it into config.json before using the bot. This should enable using git pull as an updater option.

There's also some room for improvements in terms of comparability. config.json should be checked on run to make sure all the new keys are on their places and when not update them to their default values. Or every key request by configGet() should also check default config and return value from it if key is not in production config.

File `config.json` should be replaced by `config_example.json` or something like that, and admin needs to copy it into `config.json` before using the bot. This should enable using `git pull` as an updater option. There's also some room for improvements in terms of comparability. `config.json` should be checked on run to make sure all the new keys are on their places and when not update them to their default values. Or every key request by `configGet()` should also check default config and return value from it if key is not in production config.
profitroll self-assigned this 2023-03-15 22:47:11 +02:00
profitroll referenced this issue from a commit 2023-03-17 15:44:38 +02:00
profitroll added the
Kind/Enhancement
label 2023-11-29 16:15:01 +02:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
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: profitroll/TelegramPoster#12
No description provided.