dev-server

Start, restart, and stop the FrogDB development server with configurable options.

7|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/frogdb/frogdb --skill dev-server-frogdb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-server
Source: https://github.com/frogdb/frogdb/tree/main/.claude/skills/dev-server
Command: npx skills add https://github.com/frogdb/frogdb --skill dev-server-frogdb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manages the development server lifecycle of FrogDB, including starting, restarting, and stopping instances.

Core Features & Use Cases

  • Start Dev Server: Initiate the development server with configurable options like traffic volume and port assignment.
  • Stop Dev Server: Safely terminate the running development server instance.
  • Restart Dev Server: Re-launch the server with any pending changes picked up from the source code.
  • Monitor Server Status: View the server's current status and configurations.
  • Automated Restart: Handles existing instances by automatically killing them before starting a new one to avoid port collisions.

Quick Start

To start the dev server, run the following command:

just dev

Frequently Asked Questions about dev-server

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

FAQPage Schema
How do I start a development server with Redis compatibility?

To start a development server with Redis client compatibility, initiate the FrogDB instance using the `just dev` command, which supports configurable options for testing, debug pages, and logs.

What happens if a server instance is already running on the same port?

If a server instance is already running, the dev server handles existing instances by automatically killing them before starting a new one to prevent port collisions.

How do I pick up pending source code changes during development?

To pick up pending source code changes, restart the development server to re-launch the instance and load the updated configurations and application state.

Does the FrogDB development server support read replicas and cross-slot operations?

Yes, the FrogDB development server supports read replicas, automatic state cleanup, and cross-slot operations while ensuring compatibility with Redis clients.

What is the best way to manage the development server lifecycle?

Managing the development server lifecycle involves starting, stopping, and restarting the instance with configurable options for traffic volume, port assignment, and observability.

Can I view the current status and configurations of my running development server?

Yes, you can monitor the server's current status and configurations to verify the running state and review active settings for your development environment.