GTK4 control panel for BOS (Bread Operating System)
f5d70476f0
cargo build --release alone doesn't produce a working standalone binary in Tauri v2 — embedding the frontend vs. hitting devUrl at runtime is gated by the tauri/custom-protocol Cargo feature, not the debug/release profile. The scaffold never declared it, so even release builds tried to connect to localhost:1420. Added the standard default-on custom-protocol feature (cargo tauri dev strips it via --no-default-features for dev builds); a plain `cargo build --release --locked` in src/ now produces a real standalone binary with no dev-server dependency. Also fixes vite.config.js's file-watch ignore pattern, left stale by the src-tauri -> src rename: a bare "**/src/**" glob would have also matched frontend/src itself, so it's now an absolute path scoped to the Rust project dir specifically. |
||
|---|---|---|
| .forgejo/workflows | ||
| frontend | ||
| packaging | ||
| src | ||
| .gitignore | ||
| bakery.toml | ||
| LICENSE | ||
| README.md | ||
bos-settings
System settings app for BOS (Bread Operating System) — GTK4, configures every bread* app's config plus core system settings (network, sound, power, users, firewall, snapshots, packages, AUR, firmware, Hyprland display/appearance/autostart) non-destructively.
Split out of the bos repo into its own repo so a bos-settings release doesn't require a BOS ISO release, and vice versa. Still the only pacman-packaged (not bakery-managed) bread app — see packaging/README.md.
Building
cargo build --release
Packaging / releasing
See packaging/README.md. In short: bump Cargo.toml's version, tag vX.Y.Z, push the tag to both remotes — .forgejo/workflows/package.yml builds and publishes to the [breadway] pacman repo automatically.