docker-extend

Generates personalized Dockerfile.user and docker-compose.override.yml files for each developer or CI setup, detecting DEV_MODE vs DEPLOY_MODE to modify user-facing files and reporting changes made.

23.1k|3.5k|Updated Feb 7, 2025
One-click install
npx skills add https://github.com/coleam00/Archon --skill docker-extend-coleam00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docker-extend
Source: https://github.com/coleam00/Archon/tree/main/.claude/skills/docker-extend
Command: npx skills add https://github.com/coleam00/Archon --skill docker-extend-coleam00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Personalizes Docker environments by enabling per-user tools without touching maintainer files, keeping user configs gitignored.

Core Features & Use Cases

  • Detects development vs deployment contexts to determine which Dockerfiles to modify.
  • Creates or updates Dockerfile.user and docker-compose.override.yml so each developer can customize tools locally.
  • Safely copies from example templates when files are missing and reports what was created.

Quick Start

Install or run the docker-extend workflow to generate your personalized Docker config.

Frequently Asked Questions about docker-extend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I personalize Docker configurations without modifying the root Dockerfile?

You can personalize Docker environments by using Dockerfile.user and docker-compose.override.yml files that stay gitignored. This approach isolates user-specific tool customizations, preventing accidental commits of local developer configurations to the shared repository.

What is the best way to add developer-specific tools to a shared Docker environment?

Adding developer-specific tools is best handled by generating docker-compose.override.yml and Dockerfile.user files. This method safely applies user-specific tool customizations locally without overwriting the deployment configurations maintained by the team.

Can I use docker-compose.override.yml for CI environment tool customization?

Docker-compose.override.yml supports CI environment tool customization by detecting deployment context. It safely generates or updates user-specific configuration files, ensuring CI setups requiring user-specific tool customization maintain correct deploy mode configurations.

Does generating a Dockerfile.user require existing example templates to work?

Generating a Dockerfile.user works safely even without existing example templates. The workflow automatically detects missing user-specific configuration files, creates them from available examples, and reports the newly generated files back to the developer.

Why should I keep user-specific Docker configurations gitignored?

Keeping user-specific Docker configurations gitignored prevents local developer tooling from conflicting with shared maintainer files. This guarantees individual workstation customizations remain isolated, protecting the root Dockerfile and deploy configurations from unauthorized user modifications.