Node bot guides
Everything you need to run a Node bot on Serverk: the token, variables, deployments and the console.
Start here
Deploy
Link your bot to a GitHub repository
Every push to the branch deploys your bot, and private repositories work without a token.
Add a deploy button to your repository
A README button that opens the deploy page on your bot's repository, for any public GitHub repository.
Deployments and rolling back
What happens in each deployment, and how to take your bot back to the last version that worked.
Upload your bot's code without a repository
Upload your bot folder or a zip, and ship a new version whenever you change it.
Upload rules
A folder or a zip, the limits, the folder around your files, hidden files, and what happens to .env.
How we install and start a Node project
npm, pnpm, Yarn and Bun, TypeScript and the build, the start order, and the Node version.
Your bot's data and backups
What a deployment, an upload, a rollback, a restore and a reset each replace in your bot folder, and where to keep your data so it stays.
Your bot's web address and ports
Turn on an HTTPS address and two TCP and UDP ports for your bot, for Telegram webhooks, Discord interactions and your own pages.
Tokens and variables
Add the token and your variables
Where the token goes, and how every variable reaches your bot under its own name.
Your Discord bot's token, intents and permissions
From the Developer Portal to the token in your variables, then the intents your code asks for, the invite link and the permissions.
Where to find your Telegram bot token
Create your bot with BotFather and put its token in your variables in a minute.