rector-bot-alert

Your purchase includes a license file, license.json — a small signed file that authorizes one bot instance running under one Discord application.

Activate

  1. Place license.json next to the binary:

    sudo mv license.json /opt/rector-bot-alert/license.json

  2. Restart the service:

    sudo systemctl restart alertbot

  3. Confirm activation in the logs:

    sudo journalctl -u alertbot -f

    You should see:

    [rector-bot-alert] license OK: licensee=<your name> app_id=<your application id>

How the license binds

The license is bound to your Discord application ID — the application you created per Discord application and told us when purchasing.

  • Running under the licensed application — the bot starts normally.

  • Running under any other application — the bot prints this and stops:

    [rector-bot-alert] LICENSE MISMATCH: license.json is bound to Discord application <X>, but this bot is running as application <Y>. Request a reissued license for that application ID from support.

    The fix is a reissued license for the application you actually want to run — contact support.

Moving to a new VPS

Moving machines is fine. The license is bound to the application, not the server: copy the whole /opt/rector-bot-alert directory (binary, .env, license.json) to the new VPS and start the service there. Restoring your database (see Configuration → Backups) carries your configuration with you.

For reissues and other license questions, see License terms.