Files
luxe/web/public/install.ps1
Evan Whittaker f014ead3b9 Luxe installs with curl -fsSL https://luxe.dev/install.sh | sh, edits keep a file's permissions, and the tools page charts every agent by name
- luxe.dev/install.sh redirects to the latest release's installer, and luxe.dev/install.ps1 runs
  the release's PowerShell installer under Windows' default policy, so the commands are
  `curl -fsSL https://luxe.dev/install.sh | sh` and `powershell -c "irm https://luxe.dev/install.ps1 | iex"`.
  The install tabs run shell, brew, cargo, then windows.
- The edit and write tools and format-on-save keep a file's mode, so editing a script no longer
  leaves it unrunnable.
- The tools page gives Claude Code and Codex their own columns and bars, draws Luxe's own bar in
  each group, and its terminal's window controls take macOS's colors.
- scripts/aur-pkgbuild.sh writes a luxe-bin PKGBUILD from a release, for the AUR once it reopens.
2026-10-17 20:05:01 -05:00

15 lines
991 B
PowerShell

# Luxe's installer for Windows:
#
# powershell -c "irm https://luxe.dev/install.ps1 | iex"
#
# The installer each release ships refuses to run under Windows' default execution policy, which is
# why its own instructions pass `-ExecutionPolicy ByPass`. This does the same for this PowerShell
# process alone, with nothing saved and no admin needed, then runs the latest release's installer,
# so the address never holds an installer that could drift from what the release built.
#
# A policy set by Group Policy outranks the process scope, as it outranks the command-line flag.
# Setting it then fails, and that is let pass: where the enforced policy allows the installer it runs
# anyway, and where it does not, the installer's own check says so and how to fix it.
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass -Force -ErrorAction SilentlyContinue
Invoke-RestMethod 'https://github.com/evanwhittaker/luxe/releases/latest/download/luxe-cli-installer.ps1' | Invoke-Expression