Skip to main content

2 posts tagged with "guides"

View All Tags

· 2 min read

In this guide, I'll be showing you how to deploy your sern bot with Railway.

This guide assumes you have a sern bot already set up and ready to deploy. If you don't, you can follow the Getting Started guide to set up your bot.

GitHub Repository

The first thing you'll need to deploy your bot is a GitHub repository for your bot. If you don't have one, you can create one by following the GitHub guide.

Once you have your repository set up, you can push your bot's code to the repository, and you're ready to deploy using Railway.

Railway Setup

After you have your bot's code in a GitHub repository, you'll need to create an account on Railway. You can sign up using your GitHub account at

Once you've created your account, navigate to the dashboard and click the "New Project" button. Click the "Deploy from GitHub repo" button, and select your bot's repository.

Once you've selected your repository, click the "Add Variables" button to add your bot's environment variables. You'll need your environment variables from your .env file to add to Railway. (You can also add these later if you want.)


Once you've added your environment variables, click the "Deploy" button, and Railway will start deploying your bot. Once the deployment is complete, you'll be able to see your bot's URL and logs.


Make sure you add your environment variables, and your node start script is correct in your package.json file.

If you have any issues deploying your bot, you can check the logs for any errors.

That's it! Your bot is now deployed and running on Railway. If you have any issues or questions, feel free to ask in the sern Discord server.

· 2 min read
Sr Izan

Hello everyone!

I'm Sr Izan, your fellow user and contributor.

Today I'm going to show you how to get started with sern and all its cool features.

Step 1: Install the CLI.

Install the CLI:

npm i -g @sern/cli

and then run

sern init

You can also run sern init -y if you want to use the default options.

The CLI is written in Typescript and open-sourced on Github. (thanks evo!)

Step 2: Have some way to store secrets.

Normally you'd need a way to store secrets, and the best way to do that is by installing another package: dotenv

just npm i dotenv in the project folder and add require('dotenv').config() to your import section. Then, when you login, process.env.TOKEN (or however you have it named on your .env file) should do the trick.


If you're using ESM, configure dotenv with import 'dotenv/config' instead of require('dotenv').config().

And... that's it?

Yes, that's it. Here's a little FAQ to get you started. You can also join the Discord for any problems.

Extra: Video tutorial!


Q: How do I publish a slash command?
A: Install the publish extension. Little video:

Q: Any snippet VSCode extension?
A: Yeah, just search sern Snippets made by a verified publisher called Sr Izan (haha yeah me funny!)

A: Hey, don't panic! We're here to help so, join the Discord. We're trying to get to 100 members!