reference
Reference documentation for docker-local architecture, commands, and configuration
What this skill does
# docker-local Reference
Quick reference for docker-local Laravel development environment.
## When to Use
Use this reference when you need details about:
- Service credentials and ports
- docker-local CLI commands
- File paths and project structure
- .env configuration requirements
## Service Credentials (Defaults)
| Service | Host | Port | User | Password |
|------------|----------|------|---------|-----------|
| MySQL | mysql | 3306 | laravel | secret |
| PostgreSQL | postgres | 5432 | laravel | secret |
| Redis | redis | 6379 | - | - |
| Mailpit | mailpit | 1025 | - | - |
| MinIO | minio | 9000 | minio | minio123 |
Root MySQL password: `secret`
## URLs
| Service | URL |
|--------------|----------------------------------|
| Projects | `https://{project}.test` |
| Subdomains | `https://{sub}.{project}.test` |
| Traefik | `https://traefik.localhost:8080` |
| Mailpit | `https://mail.localhost` |
| MinIO Console| `https://minio.localhost` |
## Key Commands
### Status & Health
```bash
docker-local status # Check all services and containers
docker-local doctor # Full health check with diagnostics
docker-local fix # Auto-fix common issues
```
### Container Management
```bash
docker-local up # Start all containers
docker-local down # Stop all containers
docker-local restart # Restart all containers
docker-local logs [service] # View logs (nginx, php, mysql, redis, traefik)
```
### Project Management
```bash
docker-local link # Rescan and link all projects
docker-local list # List all detected projects
docker-local make:laravel X # Create new Laravel project
docker-local open [project] # Open project in browser
```
### SSL Certificates
```bash
docker-local ssl:status # Check certificate status
docker-local ssl:regenerate # Regenerate all certificates
```
### Database
```bash
docker-local db:create X # Create MySQL database
docker-local db:mysql # Open MySQL CLI
docker-local db:postgres # Open PostgreSQL CLI
docker-local db:redis # Open Redis CLI
docker-local db:fresh # Run migrate:fresh --seed
```
### Environment
```bash
docker-local env:check # Check .env for conflicts
docker-local config # Show current configuration
```
## File Paths
| Path | Purpose |
|------|---------|
| `~/projects/` | Default projects directory |
| `~/projects/.docker-local-links/` | Symlinks for Nginx routing |
| `~/.config/docker-local/` | Configuration directory |
| `~/.config/docker-local/config.json` | Main config file |
| `~/.config/docker-local/certs/` | SSL certificates |
## Required .env Settings
For Laravel projects to work with docker-local:
```bash
APP_URL=https://myproject.test
# Database (MySQL)
DB_CONNECTION=mysql
DB_HOST=mysql
DB_PORT=3306
DB_DATABASE=myproject
DB_USERNAME=laravel
DB_PASSWORD=secret
# Redis
REDIS_HOST=redis
REDIS_PORT=6379
REDIS_PASSWORD=null
# Cache/Session/Queue isolation (unique per project)
CACHE_PREFIX=myproject_
REDIS_CACHE_DB=0
REDIS_SESSION_DB=1
REDIS_QUEUE_DB=2
# Mail
MAIL_MAILER=smtp
MAIL_HOST=mailpit
MAIL_PORT=1025
# S3/MinIO (optional)
AWS_ACCESS_KEY_ID=minio
AWS_SECRET_ACCESS_KEY=minio123
AWS_DEFAULT_REGION=us-east-1
AWS_BUCKET=myproject
AWS_ENDPOINT=http://minio:9000
AWS_USE_PATH_STYLE_ENDPOINT=true
```
## Troubleshooting Quick Reference
| Symptom | Likely Cause | Fix |
|---------|--------------|-----|
| 404 error | Missing symlink | `docker-local link` |
| "Site can't be reached" | DNS not configured | Check `/etc/hosts` or dnsmasq |
| Certificate error | Certs not generated | `docker-local ssl:regenerate` |
| Certificate still failing | mkcert not trusted | `sudo mkcert -install` |
| Container unhealthy | Service crash | `docker-local restart` |
| DB connection refused | Wrong DB_HOST | Use `mysql` not `127.0.0.1` |
## Multi-Project Isolation
Each project needs unique values to avoid conflicts:
- **Database name** - Unique per project
- **Redis DBs** - 3 DBs per project (0-2, 3-5, 6-8, etc.)
- **Cache prefix** - Unique string per project
- **MinIO bucket** - Unique per project
Use `docker-local env:check --all` to detect conflicts across projects.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.