Skip to content

docs(install): add unattended and MDM installs page for macOS - #93

Open
tanjadev wants to merge 2 commits into
mainfrom
tu/mdm-install-docs
Open

tanjadev wants to merge 2 commits into
mainfrom
tu/mdm-install-docs

Conversation

@tanjadev

Copy link
Copy Markdown
Contributor

Related: DEV-8, flox/flox-installers#529.

Adds Install Flox → Unattended and MDM installs, a page for people deploying the macOS .pkg from an MDM or a script rather than by double-clicking it. The docs had nothing on MDM, headless or unattended installs.

What the page covers

  • The plain installer -pkg ... -target / command and the architecture note.
  • What the postinstall changes on the machine (synthetic.conf, the Nix Store volume, the two LaunchDaemons, build users, /etc/nix, /usr/local/bin links, the /etc/zshrc patches).
  • Why Flox 1.16.0 and earlier fail under an MDM agent: the postinstall inherits the agent's TCC identity and cannot create /etc/fstab, so vifs fails after the volume is already created. Includes the cleanup command and the two workarounds (the MDM's native install command, or a PPPC profile granting SystemPolicySysAdminFiles to the agent binary).
  • Behaviour on machines that already have Nix: 1.16.0+ refuses a command-line install, 1.15.0 installs nothing and reports success.
  • How to verify a fleet install without relying on /etc/flox-version alone.

docs.json gets the nav entry after Install, and llms.txt is regenerated.

Checks

  • mint broken-links: no broken links in the new page (the three reported are the pre-existing /changelog/rss.xml links).

Before merging

  • The page says Flox 1.17.0 and later do not write /etc/fstab. That assumes flox/flox-installers#529 ships in the next release; adjust the version if it lands later.
  • Merge after (or together with) that installer PR.

🤖 Generated with Claude Code

Covers the plain `installer -pkg` command, what the package changes on the
machine, why 1.16.0 and earlier fail under an MDM agent (the postinstall
inherits the agent's TCC identity and cannot create /etc/fstab) with both
workarounds, the behaviour on machines that already have Nix, and how to
verify a fleet install without trusting /etc/flox-version alone.

Related: DEV-8, flox/flox-installers#529.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Sep 17, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
flox 🟢 Ready View Preview Sep 17, 2026, 4:20 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Comment thread install-flox/mdm.mdx
Comment on lines +13 to +17
Use the `x86_64-darwin` package on Intel Macs. The package refuses to install
on the wrong architecture, so a policy that ships both and lets the installer
decide is safe. Download links for the current release are on the
[Install](/install-flox/install#macos) page.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure we need to bother with this paragraph since we're deprecating x86_64-darwin soon anyway.

Suggested change
Use the `x86_64-darwin` package on Intel Macs. The package refuses to install
on the wrong architecture, so a policy that ships both and lets the installer
decide is safe. Download links for the current release are on the
[Install](/install-flox/install#macos) page.

Comment thread install-flox/mdm.mdx
Comment on lines +33 to +35
Flox 1.17.0 and later do not write `/etc/fstab`. The mount options for the
volume are set by the mount service instead.

@djsauble djsauble Sep 17, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Flox 1.17.0 hasn't been released, so a bit odd to mention it here, but also I don't think this will be true (since we haven't yet prioritized the work to change the existing /etc/fstab behavior).

@djsauble djsauble left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems more aspirational than anything, since it mentions 1.17.0 and changes to /etc/fstab behavior that we haven't committed to yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants