AXICOV CLI
A comprehensive developer guide for the Axicov CLI tool - your complete solution for project deployment with configuration metadata and automated packaging.
Axicov CLI is a powerful command-line tool designed to streamline the deployment process for projects in Axicov. It automatically validates your langchain project configuration, processes environment variables, extracts README content, creates optimized zip archives, and deploys everything to your specified API endpoint.
What Axicov CLI Does
Configuration Validation: Ensures your project configuration is correct
Automated Deployment: Deploys metadata and project files to Axicov's store
Type Safety: Full TypeScript support with proper type definitions
Built for Performance
This CLI is optimized for Bun runtime but works seamlessly with Node.js, providing fast execution and native TypeScript support.
Getting Started
Example Github repo: https://github.com/axicov/example
Prerequisites
Node.js 16.0.0 or higher (or Bun runtime)
npm, yarn, or bun package manager
A project with configuration files
Quick Start
Installation
Global Installation (Recommended, but look for version upgrades soon)
Local Installation
Verify Installation
Project Structure
A typical Axicov-enabled project structure looks like this:
Key Files
axicov.config.ts
Main configuration file
✅ Yes
README.md
Project documentation
✅ Yes
.env
Environment variables
✅ Yes
.gitignore
Files to exclude from uploading
Recommended
Configuration
Configuration File
Axicov requires an axicov.config.ts (or axicov.config.js) file in your project root. This file defines your project metadata and deployment settings.
Basic Configuration
LangChain TypeScript Configuration
Configuration Fields
name
string
Yes
Project name (must be non-empty)
description
string
Yes
Project description
readmePath
string
Yes
Path to README file (relative or absolute)
env
string
Yes
Path to environment file
params
object
Yes
Custom parameters with type definitions
port
number
Yes
Application port (1-65535)
tags
string[]
No
Optional array of project tags
Parameter Definitions
Each parameter in the params object must follow this structure:
Environment Variables
Create a .env file in your project root:
Troubleshooting
Common Issues and Solutions
1. Configuration File Not Found
Error:
Solutions:
Run
axicov initto create the configuration fileEnsure you're in the correct project directory
Check file naming: must be exactly
axicov.config.tsoraxicov.config.js
2. Invalid Configuration Structure
Error:
Solutions:
Verify parameter definitions follow the correct structure:
Check that all required fields are present and have correct types
3. Environment File Issues
Error:
Solutions:
Create the
.envfile:touch .envCheck the path in your config file matches the actual file location
Ensure proper file permissions (readable)
Environment parsing errors:
Solutions:
Each line should follow format:
KEY=valueUse
#for commentsQuote values with spaces:
KEY="value with spaces"
4. Port Configuration Issues
Error:
Solutions:
Choose a port in valid range: 1-65535
Recommended: Use ports > 1024 to avoid system port conflicts
Common choices: 3000, 8080, 8000, 5000
5. API Deployment Failures
Error:
Solutions:
Verify your API key is correct and active
Check if the API key has proper permissions
Ensure you're using the correct API endpoint
Error:
Solutions:
Check internet connectivity
Verify the API endpoint is accessible
Ensure no firewall blocking outbound requests
6. File Permission Issues
Error:
Solutions:
Create the directory:
mkdir -p distFix permissions:
chmod 755 distUse a different output path:
-o "./build"
7. Large Project Zipping Issues
Error:
Solutions:
Review your
.gitignoreto exclude unnecessary files:Remove large files that aren't needed for deployment
Consider using compression level 9: modify source code or use custom build
8. Configuration validation error
You can get a message like this:
to fix this, change this line in axicov.config.ts
to,
Debug Mode
Enable verbose output for detailed troubleshooting:
This shows:
Full configuration details
Complete metadata JSON
File scanning progress
API request/response details
Getting Help
If you encounter issues not covered here:
Check the documentation in your project's README
Verify all requirements are met (Node.js version, file structure)
Test with a minimal project to isolate the issue
Check API endpoint status if deployment fails
Best Practices
1. Project Organization
Recommended Structure:
2. Configuration Management
Type-Safe Configurations:
3. Environment Variables
Security Best Practices:
Organization:
4. README Documentation
Structure your README.md:
This guide covers the essential functionality of Axicov CLI. For advanced use cases and API integration details, refer to the official documentation or source code.
Last updated