What is the difference between sharing via Git vs. FloxHub?

Git sharing involves committing the .flox/ directory alongside your source code, which is ideal for development environments. FloxHub sharing pushes only the environment definition, making it perfect for runtime environments or shared base layers used across multiple projects.

How do I avoid conflicts when composing multiple environments?

To avoid conflicts, use unique package groups, namespace your environment variables (e.g., PROJECT_PORT instead of PORT), and ensure all hooks are idempotent so they can safely run multiple times during composition.

Can I pin specific versions of shared environments?

Yes, Flox allows you to specify a version tag in the [include] section of your manifest to ensure your composition uses a specific, immutable version of a remote environment.

How does environment composition work in Flox?

Composition allows you to merge multiple remote or local environments at build time using the [include] section in your manifest. This creates a single, deterministic environment from modular, reusable parts.

Flox Environment Sharing & Composition

Name: Flox Environment Sharing & Composition
Author: plurigrid

byplurigrid

•

部署与 DevOps

Enables seamless sharing, versioning, and composition of deterministic development and runtime environments using Flox and FloxHub.

This skill provides comprehensive guidance on managing shared Flox environments across teams and projects. It covers advanced patterns for environment composition—merging multiple deterministic environments at build time—and outlines best practices for using FloxHub for remote distribution versus Git for integrated development environments. By implementing namespacing, idempotent hooks, and service libraries, users can create modular, reusable infrastructure stacks that ensure consistency from local development to production environments.

主要功能

01Version pinning and management for shared environment dependencies.

02Remote environment management via FloxHub for sharing definitions without source code.

03Deterministic build-time environment composition using the [include] manifest section.

04Team collaboration patterns including base/specialization and service library architectures.

05Best practices for namespacing and idempotent hooks to prevent composition conflicts.

068 GitHub stars

使用场景

01Creating a 'Golden Image' base environment for an entire engineering organization to ensure tool consistency.

02Composing modular service stacks (e.g., Postgres + Redis) into specific project environments.

03Distributing runtime environments to production systems without exposing underlying source code.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add plurigrid/asi flox-sharing

For use in Claude.ai and ChatGPT

Download Skill