Maintain Your Bot

1. BOTS ARE NOT “SET IT AND FORGET IT”

Even simple bots need occasional maintenance.

That may include:

• restarting after changes

• updating code

• fixing broken modules

• refreshing tokens or API keys

• checking logs when something stops working

This is normal bot ownership.

2. PULL UPDATES FROM GITHUB

If you update the repo on GitHub and want those changes on your server, use: “git pull”

This downloads the latest changes from your repository.

💡 After pulling updates, you’ll usually need to restart Aurora.

3. RESTART AFTER CODE CHANGES

If Aurora is running and you edit the code, those changes usually won’t apply until you restart the bot.

That means:

1. stop the bot

2. save changes

3. relaunch it

4. READ THE TERMINAL WHEN SOMETHING BREAKS

The terminal is your first clue when something goes wrong.

Look for:

• missing module errors

• invalid token errors

• syntax errors

• permission errors

Even if the error looks scary, it usually points to the exact file or line causing the problem.

5. KEEP YOUR .env SAFE

Any time you move files, back up the project, or upload the repo, make sure your .env stays private.

It’s smart to:

• keep a private backup copy

• never send it to others

• reset credentials if you think they were exposed

6. DON’T OVER-MAINTAIN IT

Aurora does not need daily tweaking unless you want that.

You are allowed to let it:

• exist

• run

• do its job

Maintenance doesn’t have to become another full-time obligation.

Quick Recap - what did we do?

• Learned basic upkeep

• pulled updates

• restarted after changes

• used terminal output to troubleshoot