Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/onesoft-sudo/sudobot/llms.txt

Use this file to discover all available pages before exploring further.

Updating SudoBot involves pulling the latest code, rebuilding the project, running any new database migrations, and restarting the bot. The process is the same regardless of your deployment method, with minor differences for Docker.

Standard update (Node.js / Bun)

1

Pull the latest changes

git pull origin main
Or if you are tracking a specific release, check the GitHub Releases page and check out the desired tag:
git fetch --tags
git checkout v11.30.1
2

Rebuild the project

./blazew build
This recompiles the TypeScript source and updates the build/ directory.
3

Run database migrations

./blazew migrate
Apply any new schema migrations introduced in the update.
4

Restart the bot

pm2 restart sudobot

Docker update

1

Pull the latest code

git pull origin main
2

Rebuild the Docker image

docker compose build sudobot
3

Restart with new image

docker compose up -d sudobot
Migrations run automatically if .migration_status needs updating.

Kubernetes update

# Pull and rebuild the image
docker build -t ghcr.io/onesoft-sudo/sudobot:latest .

# Push to your registry (or use the official image)
docker push ghcr.io/onesoft-sudo/sudobot:latest

# Roll out the updated deployment
kubectl rollout restart deployment/sudobot

# Monitor the rollout
kubectl rollout status deployment/sudobot

Checking the version

The current version is in package.json:
node -e "console.log(require('./package.json').version)"
You can also find the release codename there under _meta.release_codename.
Check the CHANGELOG.md before updating to see what changed and whether any manual configuration updates are required.

Build docs developers (and LLMs) love