fix(developer-docs): use plain KEY=VALUE format in plane.env example

[sriramveeraghanta]

Summary

Ports makeplane/developer-docs#318 into this monorepo — the change landed upstream after apps/developer-docs was imported at 03dcb34, so it never made it here.

• Replace export KEY=value with plain KEY=value in the air-gapped plane.env example — docker compose --env-file does not parse shell export syntax
• Replace MACHINE_SIGNATURE=$(uuidgen) with a literal placeholder plus a :::info note telling users to run uuidgen and paste the output

Note

The upstream PR's base already had SITE_ADDRESS=https://plane.yourcompany.com in that snippet; this repo's copy did not. It's included here, since it's a required Caddy variable and part of the merged upstream state. Happy to drop the line if that omission was deliberate.

Test plan

• pnpm check:format passes
• Env snippet uses plain KEY=VALUE throughout
• The uuidgen note renders as an info container and reads clearly

https://claude.ai/code/session_01QbJp4uYoTdvYsBLeRfSJv1

Summary by CodeRabbit

• Documentation
  • Updated the air-gapped deployment guide with clearer instructions for configuring MACHINE_SIGNATURE.
  • Added guidance to define the machine signature directly in plane.env using a generated UUID.
  • Removed the previous shell-based configuration approach.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
developer-docs	Ready	Preview	Aug 21, 2026 8:11am
docs	Ready	Preview	Aug 21, 2026 8:11am

[coderabbitai]

Warning

Review limit reached

@sriramveeraghanta, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 16 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 40408a55-869e-406b-ae73-48723bf34509

📥 Commits

Reviewing files that changed from the base of the PR and between 2d088fa and 5ef3448.

📒 Files selected for processing (1)

• apps/developer-docs/docs/self-hosting/methods/airgapped-edition.md

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 748ff02d-0841-44e7-93db-a172cae24f7f

📥 Commits

Reviewing files that changed from the base of the PR and between 6ea3aa0 and 2d088fa.

📒 Files selected for processing (1)

• apps/developer-docs/docs/self-hosting/methods/airgapped-edition.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The airgapped deployment guide now documents plane.env assignments for domain variables and MACHINE_SIGNATURE. It also explains how to generate the machine signature with uuidgen.

Changes

Airgapped configuration

Layer / File(s)	Summary
Document environment variable setup apps/developer-docs/docs/self-hosting/methods/airgapped-edition.md	The guide replaces shell export commands with explicit plane.env assignments and adds uuidgen instructions for MACHINE_SIGNATURE.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 2d088

This localized documentation change is merge-ready after normal checks; no actionable merge-blocking risk remains.

Suggested reviewers: vihar

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: using plain KEY=VALUE syntax in the plane.env example.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/airgapped-env-format

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}