B1: alpha installers (NSIS, DMG), identifier com.tyrveil.lutra with data migration
- App identifier com.tyrveil.lutra (D26) in tauri.conf.json and rendezvous::APP_IDENTIFIER; a test keeps them equal. - First normal start copies settings.json, recovery/ and tools/ once from the dev.lutra.desktop directories (staging dir + rename, logged, info notification); old directories stay untouched. - Bundling on: per-user NSIS setup (English, German, Start menu, optional desktop shortcut, uninstaller) and DMG; `cargo xtask bundle` builds the platform's installer, joining the DMG backgrounds into a HiDPI TIFF on macOS. build.rs also writes icons/512x512.png for the .icns. - Installer images from the banner, designed by Amy, generated by `cargo xtask installer-images` (assets/installer/, ASSETS.md rows); approved by Daniel. - docs/install.md (SmartScreen, Gatekeeper, uninstall, data locations), README install section, architecture, development and macOS notes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
071b2a5644
commit
bd225d9e3a
22 changed files with 1367 additions and 17 deletions
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
How to set up a fresh Apple Silicon Mac (M1 or newer, macOS 14 Sonoma or newer) to build, test and run Lutra from source, and how to send a machine report back to the developers. Follow the steps in order and type the commands exactly as shown; each one is a single line for the Terminal.
|
||||
|
||||
Lutra is not signed or notarised yet, and there is no installer (DMG). You build it yourself, which is fine for the alpha: a program you build on your own Mac is not quarantined, so Gatekeeper does not block it (see [Gatekeeper](#gatekeeper-and-code-signing)).
|
||||
Lutra is not signed or notarised yet. This guide builds it from source, which is fine for the alpha: a program you build on your own Mac is not quarantined, so Gatekeeper does not block it (see [Gatekeeper](#gatekeeper-and-code-signing)).
|
||||
|
||||
## 1. Open Terminal
|
||||
|
||||
|
|
@ -177,6 +177,14 @@ The first time this asks for the Tauri CLI; install it with `cargo install tauri
|
|||
target/debug/lutra-desktop ~/Projekte/some-php-project
|
||||
```
|
||||
|
||||
## 9. Building the DMG
|
||||
|
||||
```sh
|
||||
cargo xtask bundle
|
||||
```
|
||||
|
||||
It builds the release app and packs it into `target/release/bundle/dmg/Lutra_<version>_aarch64.dmg` (the app itself is next to it in `target/release/bundle/macos/Lutra.app`). The DMG background comes in two sizes, joined with `tiffutil` so a Retina display shows the sharp one. A DMG you built yourself is not quarantined; one you copy to another Mac is, see [`install.md`](install.md#macos).
|
||||
|
||||
## Gatekeeper and code signing
|
||||
|
||||
- **Built on this Mac:** files you compile yourself (with `cargo`) carry no quarantine attribute, and the Apple Silicon linker signs them ad hoc automatically, so they run without any Gatekeeper prompt. That covers everything in this guide.
|
||||
|
|
@ -188,7 +196,7 @@ target/debug/lutra-desktop ~/Projekte/some-php-project
|
|||
|
||||
Or open it once with a right click ▸ Open (on macOS 15 and later: try to open it, then System Settings ▸ Privacy & Security ▸ Open Anyway).
|
||||
- **Phpactor:** Lutra downloads the Phpactor PHAR itself and checks its SHA-256; files that Lutra writes are not quarantined, and PHP runs the PHAR, so Gatekeeper is not involved.
|
||||
- Real signing and notarisation need an Apple Developer ID and the final app identifier (open owner decision O2); they come with the installers, after the alpha.
|
||||
- Real signing and notarisation need an Apple Developer ID; the alpha DMG is unsigned (owner decision D26), so the first start needs right-click ▸ Open or `xattr` (see [`install.md`](install.md#macos)).
|
||||
|
||||
## What is different on macOS
|
||||
|
||||
|
|
@ -196,7 +204,7 @@ target/debug/lutra-desktop ~/Projekte/some-php-project
|
|||
- **Shortcuts.** `Mod` in Lutra's keymap is ⌘ on macOS and Ctrl elsewhere.
|
||||
- **Terminal.** The integrated terminal starts your login shell (`$SHELL`, normally zsh) with `-l`, as Terminal.app does, so `~/.zprofile` runs and Homebrew's PHP and Composer are on the `PATH` even when Lutra was started from the Finder or Dock. Without a locale in the environment it sets `LANG=en_US.UTF-8`.
|
||||
- **PHP.** Lutra finds PHP on the `PATH` and, after it, in `/opt/homebrew/bin`, `/usr/local/bin` and `/opt/local/bin`, because an app started from the Finder only gets the system `PATH`. The setting `php.executable` overrides both.
|
||||
- **Data.** Settings, the recovery journal and the downloaded Phpactor live in `~/Library/Application Support/dev.lutra.desktop/`. An instance started with `--control` or `--data-dir` (as the report does) uses its own folder and shares only the Phpactor download.
|
||||
- **Data.** Settings, the recovery journal and the downloaded Phpactor live in `~/Library/Application Support/com.tyrveil.lutra/` (builds before the alpha installers used `dev.lutra.desktop/`; the first start copies its files over). An instance started with `--control` or `--data-dir` (as the report does) uses its own folder and shares only the Phpactor download.
|
||||
- **File names.** The default APFS volume ignores case, like Windows, so paths the language server reports are matched to project files without regard to case.
|
||||
|
||||
## What was checked without a Mac
|
||||
|
|
@ -218,4 +226,5 @@ These can only be checked on the Mac itself, which is what the report does:
|
|||
|
||||
| Date | Change | Summary |
|
||||
|---|---|---|
|
||||
| 2026-10-31 | minor | B1: new identifier `com.tyrveil.lutra`, building the DMG with `cargo xtask bundle` |
|
||||
| 2026-10-31 | major | A1: initial guide (setup, `cargo xtask mac-report`, Gatekeeper, macOS differences, what Windows cannot check) |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue