Compare commits

...

4 commits

Author SHA1 Message Date
Philip Peterson
176012478b Write the cask with postflight_steps and depends_on :macos
All checks were successful
CI / ci (push) Successful in 4m0s
Matches what Homebrew 7's style check wants; Ruby flight blocks are
only tolerated in third-party taps for now.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 07:44:57 -08:00
Philip Peterson
671c5e6fae README: trust the tap before installing
All checks were successful
CI / ci (push) Successful in 4m1s
Current Homebrew refuses to load casks from untrusted third-party taps.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 07:35:36 -08:00
Philip Peterson
6ef5ccd71b README: install with the Homebrew tap
Some checks are pending
CI / ci (push) Waiting to run
Also point at the Forgejo desktop workflow, not the GitHub one.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 07:33:37 -08:00
Philip Peterson
f31e861fb9 Use the public Forgejo URL in the Homebrew cask
All checks were successful
Desktop Release / Build desktop (macos) (push) Successful in 3m16s
CI / ci (push) Successful in 4m13s
Desktop Release / Publish Gitea release (push) Successful in 14s
Desktop Release / Update Homebrew tap (push) Successful in 13s
$GITHUB_SERVER_URL is the runner's own address for Forgejo
(http://localhost:3000 on mainframe), so the cask pointed its url and
homepage at localhost.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 07:21:10 -08:00
2 changed files with 29 additions and 6 deletions

View file

@ -221,6 +221,9 @@ jobs:
runs-on: ubuntu-latest
env:
TAP_REPO: ssh://git@forge.quinefoundation.com:2200/quine-global/homebrew-tap.git # Forgejo SSH is on 2200; 22 is the host's sshd
# Public address for the cask. $GITHUB_SERVER_URL is how the runner
# reaches Forgejo (http://localhost:3000 on mainframe), not a public URL.
FORGE_URL: https://forge.quinefoundation.com
steps:
- uses: https://code.forgejo.org/forgejo/download-artifact@v4
with:
@ -245,16 +248,17 @@ jobs:
sha256 arm: "$ARM_SHA",
intel: "$INTEL_SHA"
url "$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/releases/download/v#{version}/Quintodrome-#{arch}-apple-darwin.app.zip"
url "$FORGE_URL/$GITHUB_REPOSITORY/releases/download/v#{version}/Quintodrome-#{arch}-apple-darwin.app.zip"
name "Quintodrome"
desc "Desktop app wrapping the Navidrome music server"
homepage "$GITHUB_SERVER_URL/$GITHUB_REPOSITORY"
homepage "$FORGE_URL/$GITHUB_REPOSITORY"
depends_on :macos
app "Quintodrome.app"
postflight do
system_command "/usr/bin/xattr",
args: ["-dr", "com.apple.quarantine", "#{appdir}/Quintodrome.app"]
postflight_steps do
run "/usr/bin/xattr", args: ["-dr", "com.apple.quarantine", "{{appdir}}/Quintodrome.app"]
end
zap trash: [

View file

@ -32,6 +32,25 @@ Batteries included:
- **Native editing shortcuts** — Cmd+X/C/V/A/Z work in the web UI.
- **Swipe navigation** — two-finger swipe back/forward on macOS.
## Install
On macOS, with [Homebrew](https://brew.sh):
```sh
brew tap quine/tap https://forge.quinefoundation.com/quine-global/homebrew-tap.git
brew trust quine/tap
brew install --cask quintodrome
```
The tap URL is required: without one, `brew tap` assumes a GitHub repo. Homebrew
refuses to load casks from a tap you haven't trusted, hence `brew trust`. Update
with `brew upgrade --cask quintodrome`.
Or download the `.dmg` from the
[releases page](https://forge.quinefoundation.com/quine-global/quintodrome/releases)
(see [below](#macos-quintodrome-is-damaged-and-cant-be-opened) if macOS refuses
to open it).
## Quick start
```sh
@ -58,7 +77,7 @@ just bundle # or: ./desktop/scripts/build.sh
This produces the platform's packaged app under
`desktop/src-tauri/target/release/bundle/` (e.g. `macos/Quintodrome.app` on
macOS). Cross-platform binaries are built in CI — see
[`.github/workflows/desktop.yml`](.github/workflows/desktop.yml), which produces
[`.gitea/workflows/desktop.yml`](.gitea/workflows/desktop.yml), which produces
`.app`/`.dmg` on macOS and `.exe`/`.msi` on Windows for tagged releases.
> Artifacts are unsigned (no Apple/Windows code-signing certs), so users will