How does environment composition work in Flox?

Composition allows you to merge multiple environments at build-time by including them in your manifest. This enables you to combine a base OS environment with specific service environments like Postgres or Redis.

What is the difference between sharing via Git and FloxHub?

Git is recommended for development environments stored alongside source code, while FloxHub is ideal for sharing standalone, versioned environment definitions or runtime environments independently of code repositories.

How do I avoid conflicts when composing multiple environments?

To prevent collisions, you should use package groups, namespace your environment variables and functions, and ensure all hooks are idempotent so they can run safely in a merged context.

Can I pin specific versions of shared environments?

Yes, you can specify version tags in the [include] section of your Flox manifest to ensure your team uses a specific, tested version of a shared environment.

Flox Sharing & Team Collaboration

Name: Flox Sharing & Team Collaboration
Author: flox

byflox

•

Deployment & DevOps

Facilitates the sharing, composition, and synchronization of Flox environments across teams and remote repositories.

About

This skill empowers developers to manage shared development environments using FloxHub and Git integration. It provides comprehensive guidance on environment composition—merging multiple discrete environment definitions into unified, deterministic stacks—and establishes best practices for team collaboration. By leveraging remote environments and service libraries, teams can maintain modular, reproducible infrastructure that separates environment specifications from source code, ensuring consistency across local development and production runtimes.

Key Features

Deterministic environment composition using build-time merging
Dual-purpose environment design for both Git and FloxHub
3 GitHub stars
Standardized team collaboration patterns for shared stacks
Remote environment management via FloxHub synchronization
Reusable service libraries for modular infrastructure

Use Cases

Scaling a single base environment across multiple specialized frontend and backend team stacks
Orchestrating complex microservices by composing dedicated database and cache environments
Sharing reproducible runtime environments with consumers without exposing internal source code

About

Key Features

Deterministic environment composition using build-time merging
Dual-purpose environment design for both Git and FloxHub
3 GitHub stars
Standardized team collaboration patterns for shared stacks
Remote environment management via FloxHub synchronization
Reusable service libraries for modular infrastructure

Use Cases

Scaling a single base environment across multiple specialized frontend and backend team stacks
Orchestrating complex microservices by composing dedicated database and cache environments
Sharing reproducible runtime environments with consumers without exposing internal source code