You are browsing as a guest. Sign up (or log in) to start making projects!

RanDK Bot

  • 3 Devlogs
  • 1 Total hours

I have just started this project because of the "Make a Slack Bot" mission, read the Devlogs for more progress information.

Open comments for this post

39m 1s logged

[DOCUMENTATION]

I’m upgrading the documentation for my RanDK Slack Bot by writing a comprehensive, production-ready README file from scratch.

The default tutorial notes were scattered, so I wanted to create a clear guide that details our /rdk-* slash commands, the exact Slack API scopes needed, and a step-by-step local setup process.

I also mapped out a dedicated troubleshooting matrix for common Bolt framework errors and added production hosting instructions for running it 24/7 as a systemd service on Nest.

P.S. The bot is live on the server! Feel free to try it in HackClub Slack

[DOCUMENTATION]

I’m upgrading the documentation for my RanDK Slack Bot by writing a comprehensive, production-ready README file from scratch.

The default tutorial notes were scattered, so I wanted to create a clear guide that details our /rdk-* slash commands, the exact Slack API scopes needed, and a step-by-step local setup process.

I also mapped out a dedicated troubleshooting matrix for common Bolt framework errors and added production hosting instructions for running it 24/7 as a systemd service on Nest.

P.S. The bot is live on the server! Feel free to try it in HackClub Slack

Replying to @RanDK

0
27
Ship #1

I Follow the Tutorial, changed only the commands prefix to make sure its not colliding with anyone elses command. I refactor the project after that, since the tutorial is a simple all in one file code, and i just want to make it more manageable by refactoring it into manageble chunks. Waited a few minutes to get the Nest Server to host the Bot, the deployment is smooth successful. Now the bot should run 24/7. For the Demo Link, i linked it to my github account since for now theres no website for this project.

Try project → See source code →
Open comments for this post

26m 19s logged

[REFACTOR]

I’m refactoring my RanDK Bot to break apart that giant, messy index.js file from the default tutorial.

Cramming the bot config, external API calls, and individual commands into one place made the code a total headache to expand and super easy to accidentally break.

I split everything into dedicated folders for configs, services, and controllers, turning the main file into a clean switchboard that just links them together.


Now, if one command goes down, the rest of the bot stays online 24/7 on Nest, making it way easier to safely add fun new features in the future.

P.S. The bot is live on the server! Feel free to try it in HackClub Slack

  • /rdk-ping
  • /rdk-joke
  • /rdk-catfact

[REFACTOR]

I’m refactoring my RanDK Bot to break apart that giant, messy index.js file from the default tutorial.

Cramming the bot config, external API calls, and individual commands into one place made the code a total headache to expand and super easy to accidentally break.

I split everything into dedicated folders for configs, services, and controllers, turning the main file into a clean switchboard that just links them together.


Now, if one command goes down, the rest of the bot stays online 24/7 on Nest, making it way easier to safely add fun new features in the future.

P.S. The bot is live on the server! Feel free to try it in HackClub Slack

  • /rdk-ping
  • /rdk-joke
  • /rdk-catfact

Replying to @RanDK

0
11
Open comments for this post

21m 6s logged

v0.0.0

Waiting for Nest Hosting approval…

v0.0.0

Waiting for Nest Hosting approval…

Replying to @RanDK

0
16

Followers

Loading…