Skip to main content

Deployment

Deployment scenarios: development, staging &, production

🐳 Containerized / Full Deployment Workflow​

For container-based deployment — building Docker images, deploying containers, and managing lifecycle — use the following scripts:

  • Build Docker images (without deploying):

    ./scripts/build-images.sh

  • Deploy containers using existing images:

    ./scripts/deploy-all.sh

  • Build images and deploy all containers in a single step:

    ./scripts/build-deploy-all.sh

  • Stop all running containers and clean volumes (but keep built images):

    ./scripts/stop-deployed.sh

  • Remove all built images (complete clean-up):

    ./scripts/clean-built-images.sh

📦 Typical Workflows​

Development / Local Testing​

# Prepare script permissions (if not already done)
find . -name "*.sh" -type f -exec chmod +x {} \;

# Start local dev environment
./scripts/init-rundev.sh

# … work, test, debug …

# Stop when done — optionally clean data/volumes
./scripts/stop-rundev.sh        # retain data
# or
./scripts/stop-rundev.sh -a     # clean data/volumes

Containerized Deployment / Release / Production-like Setup​

# Build images + deploy all containers
./scripts/build-deploy-all.sh

# When you need to shut down containers:
./scripts/stop-deployed.sh

# To clean up all built images (free disk space / reset build cache):
./scripts/clean-built-images.sh