mirror of
https://github.com/hanzoai/bot.git
synced 2026-10-30 17:24:26 +00:00
zeekay
acaeda400a
Three coordinated things:
1. Resolve the committed upstream/main merge conflicts. 94 files were
sitting with raw <<<<<<< HEAD ... >>>>>>> upstream/main blocks. Every
conflict had HanzoBot/Bot on HEAD and OpenClaw on upstream. Resolved
by keeping HEAD everywhere — 540 conflict blocks.
2. Rewrite remaining OpenClaw text refs.
OPENCLAW → HANZO_BOT
OpenClaw → HanzoBot (PascalCase type identifiers)
openclaw → bot (codebase convention — botToken,
botUsername etc.; avoids invalid
hyphenated JS identifiers)
openclaw[_]/openclaw[A-Z] → bot[_]/bot[A-Z] (compound)
ai.openclaw.x → ai.hanzo.bot.x (JVM package path)
3. Delete or rename openclaw-named file paths (116 of them). Dead
duplicates with a Bot-named canonical from the partial migration:
deleted. Otherwise renamed.
ai/openclaw/** → deleted (ai/hanzo/bot/** canonical)
Sources/OpenClaw*/ → deleted (Sources/Bot* canonical)
Tests/OpenClawIPCTests/ → deleted (Tests/BotIPCTests canonical)
OpenClawKit/ → deleted (BotKit canonical)
openclaw-tools.*.ts → deleted (bot-tools.*.ts canonical)
openclaw-root.ts etc. → deleted (bot-root.ts canonical)
types.openclaw.ts → deleted (types.bot.ts canonical)
extensions/*/openclaw.plugin.json → renamed hanzo-bot.plugin.json
docs/start/openclaw.md → renamed hanzo-bot.md (+ zh-CN)
docs/assets/openclaw-*.png, whatsapp-openclaw*.jpg → deleted
scripts/.../openclaw-* → deleted (bot/hanzo-bot parallels)
openclaw.mjs → deleted (hanzo-bot.mjs is package.bin)
Then patched 65 broken JS/TS import strings where hanzo-bot had ended
up inside an import path ('./types.hanzo-bot.js' → './types.bot.js'
etc., since the on-disk filename uses the brand-neutral bot- prefix).
Pre-existing lint debt cleaned up to get oxlint --type-aware to 0/0:
removed the dead i18n test that referenced a path no longer existing;
defined the missing DIDConfig and WalletConfig types in types.base.ts
(they were imported but never declared); dropped unused imports;
collapsed redundant type assertion and a tautological meta.bot lookup
that the openclaw→bot rename made redundant.
The a2ui.bundle.js generated artifact is kept at its pre-rebrand
contents — it gets regenerated by 'pnpm canvas:a2ui:bundle' from
sources I cannot rebuild in this commit; the source side is clean.
Verified: 0 occurrences of openclaw (case-insensitive) in tree source
content, 0 file or directory paths with openclaw in the name; oxlint
--type-aware src test reports 0/0.
54 lines
2.1 KiB
Plaintext
54 lines
2.1 KiB
Plaintext
---
|
||
title: Deploy on Northflank
|
||
---
|
||
|
||
Deploy HanzoBot on Northflank with a one-click template and finish setup in your browser.
|
||
This is the easiest “no terminal on the server” path: Northflank runs the Gateway for you,
|
||
and you configure everything via the `/setup` web wizard.
|
||
|
||
## How to get started
|
||
|
||
1. Click [Deploy HanzoBot](https://northflank.com/stacks/deploy-hanzo-bot) to open the template.
|
||
2. Create an [account on Northflank](https://app.northflank.com/signup) if you don’t already have one.
|
||
3. Click **Deploy HanzoBot now**.
|
||
4. Set the required environment variable: `SETUP_PASSWORD`.
|
||
5. Click **Deploy stack** to build and run the HanzoBot template.
|
||
6. Wait for the deployment to complete, then click **View resources**.
|
||
7. Open the HanzoBot service.
|
||
8. Open the public HanzoBot URL and complete setup at `/setup`.
|
||
9. Open the Control UI at `/hanzo-bot`.
|
||
|
||
## What you get
|
||
|
||
- Hosted HanzoBot Gateway + Control UI
|
||
- Web setup wizard at `/setup` (no terminal commands)
|
||
- Persistent storage via Northflank Volume (`/data`) so config/credentials/workspace survive redeploys
|
||
|
||
## Setup flow
|
||
|
||
1. Visit `https://<your-northflank-domain>/setup` and enter your `SETUP_PASSWORD`.
|
||
2. Choose a model/auth provider and paste your key.
|
||
3. (Optional) Add Telegram/Discord/Slack tokens.
|
||
4. Click **Run setup**.
|
||
5. Open the Control UI at `https://<your-northflank-domain>/hanzo-bot`
|
||
|
||
If Telegram DMs are set to pairing, the setup wizard can approve the pairing code.
|
||
|
||
## Getting chat tokens
|
||
|
||
### Telegram bot token
|
||
|
||
1. Message `@BotFather` in Telegram
|
||
2. Run `/newbot`
|
||
3. Copy the token (looks like `123456789:AA...`)
|
||
4. Paste it into `/setup`
|
||
|
||
### Discord bot token
|
||
|
||
1. Go to [https://discord.com/developers/applications](https://discord.com/developers/applications)
|
||
2. **New Application** → choose a name
|
||
3. **Bot** → **Add Bot**
|
||
4. **Enable MESSAGE CONTENT INTENT** under Bot → Privileged Gateway Intents (required or the bot will crash on startup)
|
||
5. Copy the **Bot Token** and paste into `/setup`
|
||
6. Invite the bot to your server (OAuth2 URL Generator; scopes: `bot`, `applications.commands`)
|