The interface is functional with local demo data. Live hosting, provisioning and production security controls are not connected yet.
- A GitHub repository containing a supported Node.js or Python bot
- A package.json or requirements.txt at a predictable project root
- A start command that works without interactive prompts
1. Connect GitHub deliberately
The production integration is intended to request only the repository access needed for the repositories you choose. GitHub OAuth is not connected to the current prototype, so its button remains demonstrative.
2. Choose repository, branch and project root
- Select the repository explicitly.
- Choose the branch Botkeep should deploy.
- For a monorepo, point Botkeep to the directory that contains package.json or requirements.txt.
- Review the detected runtime and start command before the first build.
3. Keep configuration outside the repository
Store the Discord token and private connection strings as Botkeep secrets, not in committed .env files. Normal environment values can be configured separately when they are not confidential.
4. Deploy a new revision safely
The intended production workflow receives an authorised repository update, builds a new immutable revision and promotes it only after the build succeeds. The previous healthy deployment remains available when the new build fails. Webhooks and production builds are not active in the current frontend prototype.
Repository checklist
- No Discord token, provider token or database password in Git history.
- Lockfile committed where the ecosystem supports one.
- One documented start command.
- No node_modules, virtual environment or build cache committed.
- README notes any non-obvious runtime requirement.