docker-deployment

Configure and run Academic Events services with Docker Compose in development mode.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/werlang/event-hub --skill docker-deployment-werlang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docker-deployment
Source: https://github.com/werlang/event-hub/tree/main/.agents/skills/docker-deployment
Command: npx skills add https://github.com/werlang/event-hub --skill docker-deployment-werlang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up the Academic Events stack requires coordinating three services (API, Web, MySQL) with correct ports, environment variables, and dependency order, which is error-prone when done manually. ## Core Features & Use Cases - Stack Orchestration: Start, stop, and rebuild the api, web, and mysql services using compose.dev.yaml with a single command set. - Log and Status Inspection: Follow container logs and check service status to diagnose startup or runtime issues. - Troubleshooting Guidance: Resolve stale dependencies, unreachable services, frontend-to-API connectivity via API_URL, and API-to-MySQL host resolution. - Use Case: After cloning the repository, create a .env file and bring up the full development environment with hot-reloading API and Webpack dev server in minutes. ## Quick Start Ask the agent to start the Academic Events development stack with Docker Compose and show the API logs.

Frequently Asked Questions about docker-deployment

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

FAQPage Schema
How do I start the Academic Events stack with Docker Compose?▼

Run docker compose -f compose.dev.yaml up -d --build from the repository root after creating a .env file. This starts the api, web, and mysql services with source directories mounted for development.

How do I view Docker Compose logs for the API and web services?▼

Use docker compose -f compose.dev.yaml logs -f api web to follow logs from both services. You can also check container status with docker compose -f compose.dev.yaml ps.

What environment variables does the Docker Compose setup require?▼

The root .env file must define NODE_ENV, API_URL, JWT_SECRET, MYSQL_DATABASE, and MYSQL_ROOT_PASSWORD. The MySQL service reads the database name and root password from this file.

Why can't the frontend reach the API in Docker?▼

Check the API_URL handling in web/src/js/helpers/api.js, specifically the resolveApiUrl() and requestApi() functions. Also verify the mapped ports and host binds in the compose logs.

Why can't the API connect to MySQL outside Docker?▼

The database driver defaults to host mysql, which only resolves inside the Docker network. Local non-container runs need alternate environment configuration or host handling.

How do I fix stale dependencies in Docker containers?▼

Rebuild the images without cache using docker compose -f compose.dev.yaml build --no-cache api web, then bring the services back up with docker compose -f compose.dev.yaml up -d.