What is Enhanced Dev Env

Enhanced-dev-env is a comprehensive development environment that integrates MCP servers, the UV package manager, and Open Interpreter, designed to streamline Python development and enhance productivity.

Use cases

Use cases include initializing new Python projects, managing package dependencies, setting up testing environments, and optimizing development workflows with modern CLI tools.

How to use

To use enhanced-dev-env, you can set it up using Docker or Vagrant. For Docker, run ‘docker-compose up -d’ to start the container and access it with ‘docker-compose exec dev zsh’. For Vagrant, use ‘vagrant up’ to start the VM and ‘vagrant ssh’ to access it.

Key features

Key features include a fast UV package manager for Python, modern CLI tools, Zsh with Oh My Zsh, essential development tools like Git and Vim, Docker and Vagrant configurations, and performance tools based on Rust.

Where to use

Enhanced-dev-env is suitable for software development, particularly in Python projects, and can be utilized in various fields such as web development, data science, and machine learning.

Enhanced Development Environment with MCP Servers

A comprehensive development environment featuring UV package manager, Open Interpreter (dev branch), and Model Context Protocol servers.

🚀 Features

• UV package manager for fast Python package management
• Modern CLI tools (exa, bat, ripgrep, etc.)
• Zsh with Oh My Zsh and useful plugins
• Development tools (git, vim, tmux, etc.)
• Rust-based performance tools
• Docker and Vagrant configurations
• Optimized for Python development

🛠️ Included Tools

Python Tools

• UV package manager
• IPython
• Black (formatter)
• isort (import sorter)
• mypy (type checker)
• ruff (linter)
• pytest (testing)
• debugpy (debugging)
• pre-commit

Modern CLI Tools

• exa (modern ls)
• bat (modern cat)
• ripgrep (modern grep)
• fd-find (modern find)
• delta (git diff)
• zoxide (smart cd)
• starship (shell prompt)
• dust (modern du)
• hyperfine (benchmarking)

Development Tools

• Git
• Vim
• Tmux
• HTTPx
• Docker
• Docker Compose

🚀 Quick Start

Using Docker

# Build and start the container
docker-compose up -d

# Enter the container
docker-compose exec dev zsh

# Or use the run command
docker-compose run --rm dev

Using Vagrant

# Start the VM
vagrant up

# SSH into the VM
vagrant ssh

# Destroy the VM
vagrant destroy

📁 Directory Structure

.
├── Dockerfile           # Container definition
├── docker-compose.yml   # Container orchestration
├── Vagrantfile         # VM definition
├── .zshrc              # Shell configuration
├── workspace/          # Your projects directory
└── .config/
    └── uv/            # UV configuration

🔧 Usage

Package Management

# Install packages
python-install pandas numpy

# Create virtual environment
venv-create

# Activate virtual environment
venv-activate

# Install project dependencies
python-deps

Development Workflow

# Initialize new project
uv-init myproject

# Create project from template
uv-scaffold fastapi myapi

# Set up testing
uv-test-setup

# Check project structure
uv-project-check

Maintenance

# Clean UV cache
uv-clean

# Rebuild virtual environment
uv-venv-rebuild

# Check system
uv-doctor

⚙️ Customization

Adding Local Configuration

Create ~/.zshrc.local for machine-specific settings:

# Local environment variables
export MY_VAR="value"

# Local aliases
alias myalias="mycommand"

Modifying UV Configuration

Edit ~/.config/uv/uvconfig.toml:

[cache]
maximum_size = "10GB"
shared = true

[network]
concurrent_downloads = 8

🔍 Troubleshooting

Common Issues

1. Package Installation Problems

   uv-clean
   uv-doctor
   

2. Virtual Environment Issues

   uv-venv-rebuild
   

3. Performance Issues

   bench "your-command"  # Uses hyperfine
   

📦 Maintenance

Container Updates

# Rebuild container with updates
docker-compose build --no-cache

# Pull latest base image
docker-compose pull

VM Updates

# Update VM
vagrant provision

# Update box
vagrant box update

🔒 Security Notes

• Container runs as non-root user
• SSH keys mounted read-only
• Git config mounted read-only
• Minimal base image
• Regular security updates