Deploy using our CLI
CLI is a streamlined deployment tool for Kodus, optimized for testing and small-scale deployments.
System Requirements
Note: Internet access is only required if you plan to connect with cloud-based Git services like GitHub, GitLab, or Bitbucket. For self-hosted Git tools within your network, external internet access is optional.
Installation Guide
Need help?
Schedule a call with our founder to get help with your deployment.
1. Installing the CLI
2. Installation Process
Detailed walkthrough of the kodus install
command, including:
- Required configuration inputs
- Database setup options (local/external)
- AI API configuration (Google Vertex, OpenAI, Novita AI)
- Environment variables setup
LLM API Keys Resources
When prompted during installation, you’ll need API keys for AI providers. Use these official resources:
3. Setting Up a Reverse Proxy
To make your Kodus instance accessible from external systems (required for Code Review webhooks), you’ll need to configure a reverse proxy with Nginx.
Here’s a sample Nginx configuration:
Save this configuration to /etc/nginx/sites-available/kodus
and create a symbolic link to enable it:
Post-Installation Guide
After successfully installing Kodus with the CLI, follow these steps to get the most out of your deployment:
Completing Initial Setup
Once you access the web interface for the first time, you’ll need to:
- Create your admin account - This will be the first user with full system access
- Configure your Git provider - Connect GitHub, GitLab, or Bitbucket following the on-screen instructions
- Select repositories for analysis - Choose which code repositories Kody will review
For detailed steps on the initial configuration process, refer to our Getting Started Guide.
Updating Kodus
To update your Kodus installation to the latest version:
Enabling SSL (Recommended)
For production deployments, we strongly recommend setting up SSL:
Accessing Service Logs
Troubleshooting Common Issues
Need Advanced Troubleshooting?
For a comprehensive troubleshooting guide, see our dedicated troubleshooting documentation.