-
Notifications
You must be signed in to change notification settings - Fork 0
BettaGeorge/bot5
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
This project has given up GitHub. ([See Software Freedom Conservancy's *Give Up GitHub* site for details](https://GiveUpGitHub.org).) You can now find this project at [https://codeberg.org/BettaGeorge/bot5.git](https://codeberg.org/BettaGeorge/bot5.git) instead. Any use of this project's code by GitHub Copilot, past or present, is done without my permission. I do not consent to GitHub's use of this project's code in Copilot. I strongly encourage anyone who cares about free software to leave GitHub. See the link at the top for reasons and alternative hosting services. To start up the bot, switch into this directory and run python3 bot5.py /path/to/config with the path to a (possibly not yet existing) folder where you would like Bot5 to create its config and save files. You may omit this, in which case Bot5 defaults to creating ~/.bot5. On first startup (or if the config got deleted somehow), Bot5 will ask you to create a minimal config file. CONFIGURATION There are two configuration files: "config" contains pretty much everything you can configure, including extensions. "private.config" contains all information like passwords and authentication tokens. This is so you can safely share your config file without redacting it first. Config files are formatted as INI files [1]. A line starting with a # is a comment. It is advisable not to use the character $ in values as this may become a reserved character in future versions. Any other character is fair game. Your config file should contain at least the following information. [discord] guild = name of your server [email] from = [email protected] smtp user = [email protected] Your secret.config should contain the following. [discord] bot token = TOKEN [email] smtp pass = my super secure password!!!!1one # you may of course simply set # smtp pass = # if you do not plan on ever sending emails. Any further configuration is extension-specific and thus documented in the pertinent extension files. EXTENSIONS All extensions should be collected in the extensions folder. There are two extensions which you may not delete, namely the files logging.py and extensionmanager.py. Anything else you can delete with no ramifications. logging and extensionmanager are always loaded. The extension manager then looks at your main config file for a section called [extensions] and tries to load every extension therein (just list one extension name, without the .py ending, per line). Note that you have no control over the order in which extensions are loaded. If your extension depends on other bot5 extensions, it should instead set a proper dependency string in its code. Note that you do not need to load dependencies manually. If you load an extension that depends on another extension, the latter one is loaded automatically. If the extension is not found, startup will fail with a DependencyError. [1] https://en.wikipedia.org/wiki/INI_file
About
No description, website, or topics provided.
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published