Dashboard
Configuring the ticket dashboard
Overview The Drako Bot dashboard provides a powerful interface for managing your Discord bot. This guide will walk you through the setup and configuration process.
Prerequisites Before configuring the dashboard, ensure you have:
Node.js installed (v18.20.6)
Access to your Discord server with administrator permissions
Basic Configuration
Step 1: Discord Application Setup
Go to the Discord Developer Portal
Select your application (Bot)
Navigate to the OAuth2 section
Add a redirect URL:
For production:
http://IP:PORT/api/auth/callback
For local development:
http://localhost:PORT/api/auth/callback
Make sure to replace
IP
&PORT
with actual values.
Copy your Client ID and Client Secret from the OAuth2 page.
Step 2: Dashboard Configuration
In your config.yml
file, configure the following settings:
Replace the placeholders with your actual values:
YOUR_CLIENT_ID
: Your Discord application's Client IDYOUR_CLIENT_SECRET
: Your Discord application's Client SecretYOUR_SECURE_JWT_SECRET
: A secure random string for JWT token encryption
Step 3: Permissions Configuration
Configure role-based access control in your config.yml
:
Note: Login & pages won't be available if roles are not configured.
Advanced Configuration
Custom Navigation
You can customize the dashboard's navigation menu through the settings page:
Access the dashboard settings
Navigate to Navigation Settings
Add custom links with:
Name: Display name
URL: Target URL
Icon: FontAwesome icon name
External: Toggle for external links
Appearance Settings
Customize the dashboard's appearance:
Access dashboard settings
Navigate to Dashboard Settings
Configure:
Navigation Name: Brand name in the sidebar
Tab Name: Browser tab title
Favicon: Custom favicon URL
Security Considerations
JWT Secret
Use a strong, random string for
JWTSecret
Minimum recommended length: 32 characters
Keep this secret secure and never share it
Troubleshooting
Common Issues
Cannot Access Dashboard
Verify the correct port is open
Check if the Discord application OAuth2 settings are correct
Ensure the user has the required role
Authentication Errors
Verify
ClientID
andClientSecret
are correctCheck if the redirect URL matches exactly
Ensure
JWTSecret
is properly setEnsure that the URL has no leading /, such as http://localhost:3000/
Example: URLs should always be filled in as Url: "http://localhost:3000" and not "http://localhost:3000/"
Permission Issues
Verify role IDs are correct
Check if roles are properly assigned
Ensure the bot has necessary permissions
Last updated