Agent skill
entrypoint
Generates entrypoint.sh script for Docker container runtime environment variable injection. Replaces placeholder values in built assets with actual environment variables at container startup.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/entrypoint
SKILL.md
Entrypoint Script Skill
Purpose
Generate entrypoint.sh script for Docker container runtime environment variable injection.
Output
Create the file: entrypoint.sh in the root directory
Example File
See: examples.md in this directory for complete examples and detailed explanations.
Conditional Logic
JS Environment Substitution
- If
application_type: "standalone"→ Include the for loop that processes app*.js files with envsubst - If
application_type: "micro-frontend"→ Omit the for loop (launcher handles environment injection)
Note: The {{JS_ENV_SUBSTITUTION}} placeholder in the template should be replaced with the actual for loop code or removed based on application_type.
Notes
- Enables runtime environment variable injection into built assets
- Uses
envsubstto replace placeholders with actual environment variable values - Always processes index.html for VITE_CONTEXT_PATH
- Conditionally processes JavaScript files for standalone apps only
- Sets errexit and nounset for safer script execution
- Starts nginx in foreground mode for Docker container
- Requires gettext-base package for envsubst command
- Must be executable (chmod +x entrypoint.sh)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?