-
-
Notifications
You must be signed in to change notification settings - Fork 402
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
remind, tell: Use config name in fake .db
files
#1699
Conversation
6e93298
to
2fd7c50
Compare
Should we use a separate file at all? Now that there is #1621, this information could live in the big database. |
@kwaaak It could, but the These plugins could use custom tables, true, but their dump files are not that different from the GeoIP and malwaredomains files we already cache on disk. And those definitely aren't going into |
(Wrong browser tab, touched milestones I shouldn't have. Whoops.) |
Instead of using the bot's nick and configured host (to connect to), let's use the config `basename`. This matches the default SQLite DB filename and the names used for Sopel's log files.
2fd7c50
to
0063471
Compare
Instead of using the bot's nick and configured host (to connect to), let's use the config
basename
. This matches the default SQLite DB filename and (as of #1547) the names used for Sopel's log files.Closes #1359. Labeling "Documentation" as I need to write a new section covering this for the upgrade guide in sopel-irc/sopel.chat#17 (already referenced here in the help links given if the migration fails).