Initialize and manage a system

Use system presets to install selected development tools on macOS, Ubuntu, or Windows and enable their shell integration. Shine can also manage system settings such as private DNS separately. It does not upgrade third-party software.

Inspect before installing

List the items available for your system and inspect any prerequisites:

shine sys list
shine sys info rust

Use shine sys list --all to browse other platforms. Available items and named selections (profiles) are listed in Built-in presets.

Preview the items you want to install:

shine sys bootstrap rust mise --dry-run

The preview shows the installation steps and shell changes without applying them. Check any administrator access, downloads, or required environment variables before continuing.

Choose and install tools

Choose one method:

Goal	Command
Choose items interactively	shine sys bootstrap
Install only mise	shine sys bootstrap mise
Install Rust, then mise	shine sys bootstrap rust mise
Use the recommended selection	shine sys bootstrap --preset recommended
Use Ubuntu's minimal server selection	shine sys bootstrap --preset minimal

Before changing the system, Shine shows a plan and asks for confirmation; the default is No. Review the changes, permissions, and recovery limits. Add --verbose if you need more detail. Custom scripts run with your permissions without sandbox isolation; approve external code only after reviewing it.

Follow any installer prompts and wait for the operation to finish. Items run in order, and Shine stops at the first failure or timeout; each installer has a 30-minute limit. Use Shine's final result to confirm success, rather than a success message within an installer's log.

For scripts, see system command options, including --yes and the authorization required for external code.

Open a new terminal and check the result

Open a new shell after installation so that new commands and integrations become available. To view saved results, run:

shine sys status

This shows the latest saved result for each item, possibly from different runs. It does not check whether software is still installed or whether the current system configuration matches.

Software-specific steps, including Atuin history import, are in Ubuntu installation notes.

Use a download proxy

Add --proxy to use Shine's HTTP proxy settings. Preview first, then install:

shine sys bootstrap mise --proxy --dry-run
shine sys bootstrap mise --proxy

Configure PROXY_HOST, HTTP_PROXY_PORT, and PROXY_NO_PROXY in Shine's environment settings. The default address is http://127.0.0.1:6152; check the effective values in the preview.

On Windows, winget may first require this command in an administrator PowerShell:

winget settings --enable ProxyCommandLineOptions

Enable or disable shell integration

Shell integration makes a tool available in your terminal or enables features such as its prompt or history search. Installing selected items enables their integrations and keeps previously enabled integrations active, even when you choose a different profile.

Goal	Command
Preview disabling mise integration	shine sys profile disable mise --dry-run
Disable it	shine sys profile disable mise
Enable it again	shine sys profile enable mise

These commands change only Shine-managed shell configuration. Disabling does not uninstall the software; enabling requires it to be installed first. shine upgrade does not enable or disable these integrations. Open a new shell to use the updated configuration.

If the result says needs action, inspect the files identified in the output. Shine preserves the current file when a merge needs manual attention; a successful command exit alone does not mean the requested integration is active.

Upgrade installed software

Use the package manager or upstream tool that installed the software, such as Homebrew, apt, winget, mise, or rustup. Rerunning shine sys bootstrap skips software it detects as already installed; it does not upgrade it. shine update and shine upgrade manage Shine configuration, not third-party software versions.

For mise, use mise itself to configure and install tools and manage their versions.

Manage system settings

Use apply and uninstall for managed settings such as split-dns. Before using that item, complete the private DNS setup.

Goal	Command
Preview private DNS changes	shine sys apply split-dns --dry-run
Apply them	shine sys apply split-dns
Preview removal	shine sys uninstall split-dns --dry-run
Remove the configuration	shine sys uninstall split-dns

Review the plan before confirming. If administrator access is needed, Shine requests it after approval. Use shine sys info split-dns for details and shine sys status for saved results.

Handle failures and conflicts

• Installation failed or timed out: check the named item's error and follow its installer or package manager's repair instructions. shine sys recover does not undo software installation.
• A managed operation was interrupted: when Shine requests recovery, run shine sys recover and review its plan. Recovery completes or rolls back the interrupted operation only when the relevant state has not changed. It preserves modified resources and unrelated shell content.
• Another system operation is running: wait for it to finish. If Shine reports that the state changed, review the new plan before retrying.
• Shell configuration conflicts: inspect the files identified by Shine. Use shine sys bootstrap --force-profile only if you want to back up and replace the conflicting profile instead of preserving and merging your edits.
• Rust commands are missing on an older Ubuntu setup: upgrade Shine, run shine sys bootstrap rust, and open a new shell. This repairs integration without reinstalling detected Rust. In Bash/Zsh, you can also run . "$HOME/.cargo/env" for the current session if that file exists.

Supported shells

Shell integration supports zsh on macOS, bash and zsh on Ubuntu, and PowerShell on Windows. For automatic terminal appearance settings on Ubuntu and macOS, see terminal theme synchronization.

Retire an older local HTTP service

If you used Shine's old HTTP service, follow the cleanup steps in Upgrades and migration.