hopefully a relatively easyish to maintain alternative discord-bot with less spaghetti than our existing ones
- Go 98.7%
- Dockerfile 0.9%
- Shell 0.4%
| bot | feat: add exported Logger interface | |
| cmd/gardener | feat: readd + complete report module | |
| config | make config.Unmarshal search a single directory for files | |
| internal | feat: add exported Logger interface | |
| modules | chore(modules/levels): clean up database schema | |
| .gitignore | update gitignore | |
| build.sh | chore: update module path | |
| docker-compose.yml | make config.Unmarshal search a single directory for files | |
| Dockerfile | chore: update module path | |
| go.mod | chore: update dependencies | |
| go.sum | chore: update dependencies | |
| LICENSE | Initial commit | |
| README.md | feat: add configuration tables + methods for interacting with them | |
gardenerbot
hopefully a relatively easyish to maintain alternative discord-bot with less spaghetti than our existing ones
requirements
- Go 1.17
- PostgreSQL 12 or later (latest version recommended, may work with versions <12 but not tested)
running
this bot doesn't do much so far
to run it in its current state, create a file named gardener.yaml in the config/ directory, and add the following:
auth:token:discordTokenHeredatabase:postgresql://postgres:postgres@localhost/postgresreplacing token with your bot's discord token and database with your database url
if you're using PostgreSQL 12 or earlier, and don't have the bot connect as a superuser,
you will have to run CREATE EXTENSION hstore; as superuser on the database you created before running the bot for the first time
(because hstore is not a trusted module before PostgreSQL 13)