#Development Services Management

This guide covers the essential development services for Flash Turbo CMS and how to manage them.

#Services Overview

The Flash Turbo CMS requires four essential services for local development:

1. MongoDB - Database server
2. Redis - Cache and session storage
3. MinIO - S3-compatible object storage
4. MailHog - SMTP testing server

#Quick Start

#Using the Services Script (Recommended)

# Interactive mode
./manage services

# Start all services
./manage s start all

# Check status
./manage s status

# Stop specific service
./manage s stop mongodb

#Using Docker Compose (Alternative)

cd Docker-Tools

# Start all services
docker-compose up -d

# Stop all services
docker-compose down

#Service Details

#MongoDB

• Port: 27017
• Volume: mongodb_data
• Environment: DATABASE_URI=mongodb://0.0.0.0:27017
• Admin Credentials: admin/admin

#Redis

• Port: 6379
• Volume: redis_data
• Environment: REDIS_URL=redis://localhost:6379
• Version: Redis 7 Alpine (lightweight, fast)

#MinIO S3 Storage

• API Port: 9000
• Console Port: 9001
• Volume: minio_data
• Environment:

  S3_ACCESS_KEY=bhuvan
  S3_SECRET_KEY=bhuvanbm7
  S3_ENDPOINT=http://localhost:9000
  S3_BUCKET=local
  

• Web Console: http://localhost:9001

#MailHog

• SMTP Port: 1025
• Web UI Port: 8025
• Environment:

  SMTP_HOST=localhost
  SMTP_PORT=1025
  SMTP_SECURE=false
  

• Web UI: http://localhost:8025

#Environment Configuration

Add these to your .env file to use local services:

# Database (Local MongoDB)
DATABASE_URI=mongodb://0.0.0.0:27017

# Cache (Local Redis)
REDIS_URL=redis://localhost:6379

# S3 Storage (Local MinIO)
S3_ACCESS_KEY=bhuvan
S3_SECRET_KEY=bhuvanbm7
S3_ENDPOINT=http://localhost:9000
S3_REGION=local
S3_FORCE_PATH_STYLE=true
S3_BUCKET=local

# Email (Local MailHog)
SMTP_HOST=localhost
SMTP_USER=admin@localhost
SMTP_PASS=Flash@Cms@25
SMTP_PORT=1025
SMTP_SECURE=false

#Services Script Commands

./manage services [command] [service]

Commands:
  status              Show status of all services
  start [service]     Start service(s) - mongodb, minio, mailhog, or 'all'
  stop [service]      Stop service(s) - mongodb, minio, mailhog, or 'all'
  remove [service]    Remove service and optionally its data
  create-bucket       Create MinIO 'local' bucket
  help               Show help

Examples:
  ./manage s                  # Interactive mode
  ./manage s status           # Show service status
  ./manage s start all        # Start all services
  ./manage s start mongodb    # Start only MongoDB
  ./manage s stop minio       # Stop only MinIO
  ./manage s create-bucket    # Create MinIO bucket

#Data Safety & Recovery

IMPORTANT: Service data is stored in persistent volumes:

• mongodb_data - MongoDB database files
• minio_data - MinIO object storage files

#Data Persistence

Data survives:

• Container stops/starts
• Container recreation
• System reboots (with restart policies)

#Recovery After Accidental Removal

If containers are accidentally removed, data persists in volumes. Simply restart services:

./manage s start all

#Backup Volumes

# Backup MongoDB data
podman run --rm -v mongodb_data:/data -v $(pwd):/backup alpine tar czf /backup/mongodb-backup.tar.gz -C /data .

# Backup MinIO data  
podman run --rm -v minio_data:/data -v $(pwd):/backup alpine tar czf /backup/minio-backup.tar.gz -C /data .

#Troubleshooting

#Port Conflicts

If ports are in use, check what's using them:

sudo lsof -i :27017  # MongoDB
sudo lsof -i :9000   # MinIO API
sudo lsof -i :9001   # MinIO Console
sudo lsof -i :1025   # MailHog SMTP
sudo lsof -i :8025   # MailHog Web UI

#Container Issues

# Check container logs
podman logs mongodb
podman logs minio
podman logs mailhog

# Restart a problematic service
./manage s stop mongodb
./manage s start mongodb

#Volume Issues

# List volumes
podman volume ls

# Inspect volume
podman volume inspect mongodb_data

# Remove volume (DATA LOSS!)
podman volume rm mongodb_data

#Connection Testing

# Test MongoDB
podman exec mongodb mongosh --eval "db.adminCommand('ping')"

# Test MinIO
curl -I http://localhost:9000/minio/health/live

# Test MailHog
curl -s -o /dev/null -w "%{http_code}" http://localhost:8025/

#Security Notes

• MongoDB has basic authentication (admin/admin)
• MinIO uses your specified credentials (bhuvan/bhuvanbm7)
• MailHog has no authentication (development only)
• All services use host networking for simplicity
• Services are isolated in containers

#Service Dependencies

Flash Turbo CMS depends on these services being available:

• Database connection will fail without MongoDB
• File uploads will fail without MinIO
• Email sending will fail without MailHog

Always ensure services are running before starting the application.