Check if the `ORBIT_ENABLE_SCRIPTS` plist variable exists and set or add it accordingly in the plist. Prior to this change, if the variable was not already present on the host, the script would fail to set the variable. This change also sets the `plist_path` variable, which was missing in the original script. # Checklist for submitter If some of the following don't apply, delete the relevant line. - [x] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements), JS inline code is prevented especially for url redirects, and untrusted data interpolated into shell scripts/commands is validated against shell metacharacters. ## Testing - [x] QA'd all new/changed functionality manually ## fleetd/orbit/Fleet Desktop - [x] Verified compatibility with the latest released version of Fleet (see [Must rule](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/workflows/fleetd-development-and-release-strategy.md)) - [x] Verified that fleetd runs on macOS, Linux and Windows <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Improved macOS setup script to more reliably configure the launchd environment variable: it now detects whether the variable exists before updating or adding it, handles errors silently during probes, uses a single plist path variable instead of a hardcoded path, and ensures the service is restarted with the updated configuration. <!-- review_stack_entry_start --> [](https://app.coderabbit.ai/change-stack/fleetdm/fleet/pull/46100?utm_source=github_walkthrough&utm_medium=github&utm_campaign=change_stack) <!-- review_stack_entry_end --> <!-- end of auto-generated comment: release notes by coderabbit.ai -->
assets Directory
This directory is used by the frontend build tool to store generated frontend build assets, such as JavaScript bundles, CSS files, and other static resources (images, fonts, etc.) that are produced during the build process.
Key Points
- Do not commit generated files: All files in this directory are generated automatically and are git-ignored. They should not be committed to version control.
- Not for static files: Do not place unrelated static files (like PDFs, config profiles, or documentation) here. Use a separate directory for non-UI assets.
- Regenerated on build: These files are recreated every time you run the frontend build process.