What problem does it solve? Setting up and maintaining the Toollab local development environment involves two Docker Compose stacks (Laravel API and Nuxt front), an external shared network, UID/GID alignment, named volumes, and config caching pitfalls. This Skill consolidates every startup, reset, and troubleshooting procedure so developers avoid broken permissions, stale config, and lost data. ## Core Features & Use Cases - First-time setup: Creates the external dev_toollab network, aligns .env UID/GID with the host, builds both stacks, and runs migrations with seeds. - Daily operations: Provides ready-to-use commands for logs, artisan tasks (migrate, tinker, queue, pest, pint), database access, and container lifecycle management. - Database reset: Resets the database either with demo seed data or cleanly with ProductionSeeder plus a super admin account. - Troubleshooting table: Diagnoses common failures such as missing network, permission denied on vendor/storage, occupied ports, 413 upload limits, 502 nginx errors, and ineffective .env changes. - Use Case: A developer clones the repo on a new machine, follows the Skill to create the network and fix .env values, and has the API at localhost:8000 and the Nuxt front at localhost:3000 running with seeded data in minutes. ## Quick Start Ask the assistant to start the Toollab Docker development environment and seed the database with demo data.
