What is the difference between personal and organization catalogs?

Personal catalogs are private to the user and ideal for testing, while organization catalogs allow shared access for team members to search for and install packages.

Can I automate Flox publishing in my CI/CD pipeline?

Yes, you can use the flox auth login --token command with a FLOX_AUTH_TOKEN secret to automate the publishing process in tools like GitHub Actions or GitLab CI.

Why does Flox perform a clean build before publishing?

Flox performs a clean build in a temporary location to ensure reproducibility, verifying that the package doesn't rely on uncommitted local files or specific machine state.

Does flox-publish include my source code in the package?

No, published packages contain only the binaries and compiled artifacts located in the $out directory, keeping your source code separate from the distribution.

How do users install a package after it has been published?

Once published, users can find and install your package using the command 'flox install / ' in any Flox environment.

Flox Package Publishing

Name: Flox Package Publishing
Author: flox

byflox

•

Deployment & DevOps

Publishes and distributes pre-built packages to Flox catalogs for seamless cross-environment sharing.

About

This skill empowers Claude to manage the complete lifecycle of Flox package distribution, enabling the separation of source-heavy development environments from lightweight runtime environments. It guides users through authenticating, defining build manifests, validating reproducible builds in clean environments, and publishing artifacts to personal or organizational catalogs. By leveraging this skill, teams can share optimized binaries without exposing source code, implement consistent versioning strategies, and automate publishing workflows within CI/CD pipelines.

Key Features

Management of runtime versus build-time dependency separation
Integration patterns for CI/CD workflows like GitHub Actions
Multi-strategy versioning support including SemVer and Git-based tags
3 GitHub stars
Clean build validation to ensure environment reproducibility
Automated package publishing to personal and organization catalogs

Use Cases

Distributing proprietary software binaries across a team without sharing source code
Creating lightweight production environments containing only necessary runtime artifacts
Testing package variants in a personal namespace before promoting to organization catalogs

About

Key Features

Management of runtime versus build-time dependency separation
Integration patterns for CI/CD workflows like GitHub Actions
Multi-strategy versioning support including SemVer and Git-based tags
3 GitHub stars
Clean build validation to ensure environment reproducibility
Automated package publishing to personal and organization catalogs

Use Cases

Distributing proprietary software binaries across a team without sharing source code
Creating lightweight production environments containing only necessary runtime artifacts
Testing package variants in a personal namespace before promoting to organization catalogs