#Docker Container Management - Flash Turbo CMS

#🎯 Production-Ready Container Management

Complete Docker/Podman container management system optimized for Flash Turbo CMS Turborepo monorepo.

#🚀 Quick Start

#Essential Commands

# Build and run with Bun (recommended - ~374MB)
./manage c update Dockerfile.bun-optimized

# Interactive mode (shows all options)
./manage c

# View logs
./manage c logs

# Stop container
./manage c stop

#📦 Available Dockerfiles

Dockerfile	Size	Description	Status
configs/Dockerfile.bun-optimized	~374MB	✅ Bun runtime - RECOMMENDED	Production Ready
configs/Dockerfile.nodejs-optimized	~500MB	Node.js runtime - Alternative	Production Ready
configs/Dockerfile.nodejs	~7.7GB	Node.js runtime - Legacy	Deprecated
Dockerfile	~500MB	Node.js runtime (app dir)	Legacy
Dockerfile.bun-clean	~400MB	Bun runtime (clean)	Legacy

#🛠️ Complete Command Reference

Command	Usage	Description
build	./manage c build [Dockerfile]	Build Docker image only
run	./manage c run [Dockerfile]	Build and run container (with env file selection)
update	./manage c update [Dockerfile]	Full update (build + run + cleanup prompt)
stop	./manage c stop	Stop and remove container
logs	./manage c logs	View container logs (Ctrl+C to exit)
shell	./manage c shell	Open shell in running container
cleanup	./manage c cleanup	Interactive cleanup with multiple options
prune	./manage c prune	System prune (remove unused resources)
help	./manage c help	Show detailed help

#🏃‍♂️ Runtime Environment Selection

When running containers, you can select which environment file to use:

• .env - Default development environment
• .env.local - Local overrides
• .env.production - Production environment
• .env.staging - Staging environment
• No env file - Run without environment variables

Example:

./manage c run
# Will prompt to select environment file for container runtime

#🧹 Intelligent Cleanup System

After successful run or update commands, the system automatically prompts for cleanup:

1. Remove old versions only - Keeps current image, removes previous versions
2. Remove ALL flash-turbo-cms images - Complete image cleanup (stops container first)
3. System prune - Remove unused containers, networks, and dangling images
4. Full cleanup - Stop container + remove all images + system prune
5. Skip cleanup - Continue without cleanup

#🔧 Advanced Features

#Multi-Tag System

Each build creates multiple tags for the same image:

Bun Optimized builds (configs/Dockerfile.bun-optimized):

• flash-turbo-cms:1.2.8-bun-optimized (version-specific)
• flash-turbo-cms:latest (generic latest)
• flash-turbo-cms:latest-bun (latest bun)
• flash-turbo-cms:bun-optimized (build type)
• flash-turbo-cms:recommended (recommended tag)

#Environment Variables in Build

All environment variables from .env are automatically passed to build process as --build-arg parameters.

#Background Container Execution

Containers run in background mode with proper health checks and status reporting.

#📋 Production Deployment

1. Recommended Setup: Use configs/Dockerfile.bun-optimized for production
2. Environment: Use .env.production for production environment variables
3. Size: Optimized builds result in ~374MB final images
4. Performance: Bun runtime provides faster startup and better performance

#🔍 Troubleshooting

#Check Container Status

podman ps -a                          # List all containers
./manage c logs                       # View application logs
curl -I http://localhost:3000         # Test if app is responding

#Image Information

podman images | grep flash-turbo-cms  # List all project images
./manage c cleanup                    # Interactive cleanup options

#Common Issues

• Port conflicts: Make sure port 3000 is available
• Environment variables: Verify .env file exists and has correct values
• Build failures: Check if all dependencies are properly installed
• Container won't start: Review logs with ./manage c logs