Community Edition

Deployment Guide

Deploy Crucible Community Edition to production environments including cloud providers and on-premise infrastructure.

Production Checklist

  • Use production-grade database (PostgreSQL with backups)
  • Enable HTTPS/TLS for all connections
  • Configure secure environment variables
  • Set up monitoring and logging
  • Configure backup strategy for database
  • Set up reverse proxy (nginx/traefik)
  • Configure firewall rules
  • Enable rate limiting

Docker Compose Production

# Use production compose file
docker compose -f docker-compose.prod.yml up -d

# Or customize for your environment
docker compose -f docker-compose.yml up -d
bash

Cloud Providers

AWS

  • Use ECS/Fargate for container orchestration
  • RDS PostgreSQL for database
  • Application Load Balancer for HTTPS
  • S3 for artifact storage
  • CloudWatch for monitoring

Google Cloud

  • Cloud Run for serverless containers
  • Cloud SQL for PostgreSQL
  • Cloud Storage for artifacts
  • Cloud Load Balancing

Azure

  • Container Instances or AKS
  • Azure Database for PostgreSQL
  • Azure Blob Storage for artifacts
  • Application Gateway

On-Premise Deployment

For on-premise deployments:

  • Ensure Docker and Docker Compose are installed
  • Configure internal network access
  • Set up internal DNS if needed
  • Configure firewall rules for model API access
  • Use internal PostgreSQL instance
  • Configure backup solutions

Scaling

To scale Crucible:

  • Run multiple API instances behind a load balancer
  • Use connection pooling for database
  • Consider Redis for session state if needed
  • Scale database resources as needed
  • Monitor resource usage and adjust