dual-env

Name: dual-env
Availability: InStock
Author: langware-labs

Run production and development flow-cli environments simultaneously with shared resources.

5|1|Updated Mar 15, 2026

Search Tags:#workflow #development #production #environment management #local setup #flow-cli

Ready to run

npx skills add https://github.com/langware-labs/flowpad --skill dual-env

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dual-env
Source: https://github.com/langware-labs/flowpad/tree/main/.claude/skills/dual-env
Command: npx skills add https://github.com/langware-labs/flowpad --skill dual-env

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill enables developers to run and manage both production and development instances of flow-cli simultaneously on their local machines, simplifying testing and deployment workflows.

Core Features & Use Cases

Dual Mode Operation: Set up and coordinate two flow-cli environments for development and production.
Shared State Management: Maintain consistent environment variables, databases, and configurations across both instances.
Use Case: A developer needs to test new features locally without disrupting the stable production setup, ensuring quick iteration and reliable deployment.

Quick Start

Check out the repository, set up both instances with customized ports and shared directories, then start them separately for parallel operation.

Frequently Asked Questions about dual-env

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

FAQPage Schema

How do I run production and development flow-cli environments side by side?▼

To run production and development flow-cli environments side by side, you must configure separate environment variables, port settings, and repository folders for each instance before starting them individually for parallel operation.

Why does testing new features locally disrupt my stable production flow-cli setup?▼

Testing new features disrupts production because both environments typically share the same resources. Using a dual-environment setup isolates development and production instances while maintaining shared state like databases and configurations across both.

How do I set up local flow-cli instances with customized ports and shared directories?▼

To set up local flow-cli instances with customized ports and shared directories, check out the repository, configure the environment variables and port settings, establish shared directories, and then start the two instances separately.

Do I need to configure environment variables to manage isolated flow-cli workflows?▼

Yes, you need to configure environment variables, port settings, and repository folders to manage isolated flow-cli workflows. This configuration enables seamless testing and deployment while keeping development and production environments coordinated.

What is the best way to manage shared state across development and production environments?▼

The best way to manage shared state across development and production environments is using a dual-environment setup that maintains consistent environment variables, databases, and configurations across both isolated flow-cli instances simultaneously.

Can I use dual environment management for simultaneous testing and deployment?▼

Yes, dual environment management supports simultaneous testing and deployment. It allows developers to test new features locally without disrupting the stable production setup, ensuring quick iteration and reliable deployment workflows.