Welcome!

This is the KavitaBot support thread!

 

KavitaBot is a Docker app I wrote that lets Discord users generate their own Kavita invite links. The bot will DM the user the link in Discord along with Kavita emailing it to them. All messages are ephemeral, can be dismissed, and can only be seen by the user that used the command.

 

Installation:

This container only requires 5 environment variables and internet access.

Environment Variables:
 

KAVITA_OPDS_URL – The full OPDS URL from an account in your Kavita with appropriate privileges.
DISCORD_BOT_TKN – The token of your discord bot.
DISCORD_SVR_ID – The ID of your Discord server to enable forced sync update.
DISCORD_CHAN_ID – The channel ID where you want the bot to accept commands.
DISCORD_ROLE_ID – The user role ID you want to be required to use the bot.

 

Official Links:

Docker Hub: https://hub.docker.com/r/dmtnt/kavitabot

GitHub: https://github.com/dmtnt0/kavitabot

Documentation: https://github.com/dmtnt0/kavitabot/wiki/KavitaBot-Wiki  [Updated: 06MAR25]

Edited March 6, 20251 yr by DMTNT

UPDATE: v0.2.1

• Fixed an error that was introduced with v0.2.0 that would occur when the bot would try to validate a user invite request against Kavita existing users.

 

UPDATE: v0.2.0

• Fixed the channel ID not being optional.
• Added a new function to test if the user requesting an invite already has an account and if it's pending or active.
• Added a response for if a user requests an invite that already has an account pending.
• Added a response for if a user requests an invite that already has an active account. This will also include the domain url (i.e. https://domain.tld)
• Added a response to a successful invite directing the user to check their DMs for the invite code.
• Performed some housekeeping tasks.

PLANNED:

• (definitely) Add a check for the domain link provided when a user has an active account to include any base url.
• (possibly) A function to validate Kavita users against Discord users and disable / delete users not present. Environment variables would enable/disable this feature and allow custom schedules. Feedback on this is welcome.

NOTES:

• Any suggestions for functionality are welcome. This is an ongoing project that I want to make as useful as possible since, last I checked, the Kavita devs have no intentions to implement a Single Sign On feature.

Edited March 29, 20251 yr by DMTNT

Reserved