start-local-dev

Orchestrate PostgreSQL, API, Importer, and Evaluator startup order locally via task runner commands.

1|1|Updated Dec 16, 2023
One-click install
npx skills add https://github.com/sjtw/tarkov-build-optimiser --skill start-local-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-local-dev
Source: https://github.com/sjtw/tarkov-build-optimiser/tree/main/.cursor/skills/start-local-dev
Command: npx skills add https://github.com/sjtw/tarkov-build-optimiser --skill start-local-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating multiple local services for development can be error-prone and time-consuming, especially when booting a database, API, importer, and evaluator in the correct order.

Core Features & Use Cases

  • Orchestrates startup and shutdown of core services (PostgreSQL, API, Importer, Evaluator) to streamline local development.
  • Ensures correct startup order and dependency readiness, reducing setup errors.
  • Supports repeatable workflows for onboarding, testing, and feature development.

Quick Start

Start and manage the complete local development stack by booting the database, API, importer, and evaluator in the recommended order.

Frequently Asked Questions about start-local-dev

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

FAQPage Schema
How do I orchestrate a multi-service local development stack with Docker?

Orchestrating a local development stack uses a task runner to launch Docker services like PostgreSQL, API, Importer, and Evaluator in a reproducible manner. It enforces correct startup order and dependency readiness to streamline local development workflows.

How do I manage service lifecycles and startup order for local development?

Managing service lifecycles requires enforcing strict startup order for core services like PostgreSQL, API, Importer, and Evaluator. The task runner exposes concise, repeatable commands to coordinate booting and shutting down the development environment.

Why does my local development stack fail when booting multiple services?

Local development stacks fail when multi-service startup order and dependency readiness are not enforced. Orchestrating the database, API, importer, and evaluator in a reproducible sequence reduces setup errors and ensures proper coordination.

Do I need a task runner to bootstrap a PostgreSQL and API development environment?

Bootstrapping a PostgreSQL and API development environment requires a task runner to apply repeatable workflows. It coordinates the startup and shutdown of the database, API, importer, and evaluator to reduce onboarding and testing errors.

What's the best way to coordinate a database, API, importer, and evaluator for local testing?

The best way to coordinate these services is using a task runner to orchestrate their lifecycles in a reproducible manner. It enforces the correct startup order and dependency readiness for the PostgreSQL database, API, importer, and evaluator.